Skip to content
Commits on May 9, 2013
  1. Move script to the very right of rdebug-vim command

    This way, we can easily pass additional params to the script
    committed May 9, 2013
Commits on Apr 17, 2013
  1. Get only the PID from the rdebug-vim output [#82]

    So, if rdebug-vim produces any warnings, they should not affect the
    plugin's work
    committed Apr 16, 2013
Commits on Mar 20, 2013
  1. Fix stupid bug - incorrect Server.is_running()

    It should actually return false when there is no pid, not vice versa :)
    committed Mar 19, 2013
Commits on Mar 19, 2013
  1. Make plugin work with debugger-xml through UNIX sockets

    This is a pretty big rewriting of the plugin.
    
    I added support of the different printers to the 'debugger' gem, and
    that allowed me to create new gem, 'debugger-xml', which is a 'debugger'
    extension, and allows to display results not in plain text, but in XML
    format, compatible with 'ruby-debug-ide' gem.
    
    In debugger-xml, I added support of UNIX sockets, so now
    vim-ruby-debugger doesn't need additional Ruby daemon
    (bin/ruby_debugger.rb) for work anymore. Now, vim-ruby-debugger just
    sends message through UNIX socket directly to debugger-xml, and
    debugger-xml will poke vim-ruby-debugger when new event happens or
    a command is handled and has something to output.
    
    Thanks to all that stuff, vim-ruby-debugger works a bit faster now,
    because I don't use TCP anymore, and because I got rid of one additional
    hop (from vim-ruby-debugger to bin/ruby_debugger.rb), and also more
    robust, since there is no additional daemon, and no need to handle
    (i.e. start/stop) it anymore.
    
    I also dropped Windows support, but I actually am not sure it worked
    before - I even don't have Windows to check it out. If you still need
    Windows support, you may try to use 'v1.0' branch, or contribute to
    here. :)
    
    Also, removed the requirement of 'lsof', debugger-xml now explicitly
    tells its PID before daemonizing (I used to use lsof before to get PID of
    bin/ruby_debugger.rb and rdebug-ide)
    committed Mar 18, 2013
Commits on Mar 14, 2013
  1. Update README again

    committed Mar 13, 2013
  2. Update README

    committed Mar 13, 2013
Commits on Feb 5, 2013
  1. Update screenshot location

    committed Feb 4, 2013
  2. Add screenshot

    committed Feb 4, 2013
Commits on Dec 30, 2012
  1. Fix regexp for the eval command

    I.e. now it can parse both eval XML commands like:
    <eval expression="2 + 2" value="4"/>
    and
    <eval expression="2 + 2" value="4" />
    (i.e. with trailing space)
    committed Dec 30, 2012
Commits on May 7, 2012
  1. Merge pull request #70 from bigloser/add_single_test_option_for_rspec

    add RdbTestSingle command option that will pass line to rspec command
    Anton Astashov committed May 6, 2012
Commits on Apr 13, 2012
  1. Add the g:ruby_debugger_no_maps setting

    You can specify in your .vimrc:
    
        let g:ruby_debugger_no_maps = 1
    
    and the plugin won't set default key bindings (mappings).
    It may be useful if other plugins conflict with the mappings of
    vim-ruby-debugger
    committed Apr 13, 2012
Commits on Dec 27, 2011
  1. Merge pull request #62 from ecoffey/macvim_readme_instructions

    Macvim readme instructions
    Anton Astashov committed Dec 26, 2011
  2. Add -Itest for :RdbTest for Test::Unit tests

    Now Test::Unit tests run with -Itest option, like:
    
        ruby -Itest test/unit/user_test.rb
    
    This way, you don't need to specify the full path to test_helper.rb in
    your tests, like:
    
    	  require File.expand_path('../../test_helper.rb', __FILE__)
    
    Now you just can add:
    
        require 'test_helper'
    
    like you usually do in your tests.
    committed Dec 27, 2011
Commits on Oct 2, 2011
  1. Merge pull request #63 from ecoffey/statusline

    Add ruby_debugger#statusline
    Anton Astashov committed Oct 1, 2011
Commits on Sep 22, 2011
  1. updated the help text

    Eoin Coffey committed Sep 22, 2011
Commits on Sep 21, 2011
  1. Add ruby_debugger#statusline

    Eoin Coffey committed Sep 21, 2011
Commits on Sep 14, 2011
  1. @ecoffey

    Change formatting.

    ecoffey committed Sep 14, 2011
  2. Change formatting and explanations

    Eoin Coffey committed Sep 14, 2011
  3. Add MacVim specific instructions to README

    Eoin Coffey committed Sep 14, 2011
Commits on Aug 14, 2011
  1. Update final files (autoload/ruby_debugger.vim)

    Anton Astashov committed Aug 15, 2011
  2. Merge pull request #55 from stephenprater/efficient_logging

    efficient logging
    Anton Astashov committed Aug 14, 2011
Commits on Aug 13, 2011
  1. change writing strategy to match vims.

    A.G. Russell Knives committed Aug 13, 2011
Commits on Aug 11, 2011
  1. spaces solved

    A.G. Russell Knives committed Aug 11, 2011
Commits on Aug 8, 2011
  1. efficient logging

    A.G. Russell Knives committed Aug 8, 2011
Commits on Jul 11, 2011
  1. Add default command for :Rdebugger

    Now you can specify a default command, i.e. what will be run when you
    write ':Rdebugger' without an argument. E.g. if you mostly use Rails 3,
    then you may want to add such line to your .vimrc:
    
      let g:ruby_debugger_default_script = 'script/rails s'
    
    and then you'll be able to run Rails 3 apps just by :Rdebugger command.
    Anton Astashov committed Jul 11, 2011
Commits on Jul 5, 2011
  1. Fix getting absolute path

    Anton Astashov committed Jul 5, 2011
Commits on May 1, 2011
  1. Fix of the issue #41

    The error of missing self.debugger_id was happened due to incorrect
    returning of control from ruby_debugger.rb when start command is given.
    Adding of stripping of leading/trailing whitespaces in comparement fixed
    that issue.
    Anton Astashov committed May 1, 2011
Commits on Apr 30, 2011
  1. Merge pull request #46 from rweng/master.

    It really works, thanks, rweng.
    Anton Astashov committed Apr 30, 2011
Commits on Apr 6, 2011
  1. @rweng

    fix 'too many file names'

    rweng committed Apr 6, 2011
Commits on Feb 5, 2011
  1. Update README and the plugin's help file.

    Anton Astashov committed Feb 5, 2011
  2. Move all source files to src dir, move all working files out of vim dir

    Now all files which should be loaded by vim are placed in the root dir
    of the repo, all 'development' files are placed into 'src' dir. This
    way, it should be easier to handle the plugin by git submodules when
    using it with pathogen.
    Anton Astashov committed Feb 5, 2011
Commits on Feb 3, 2011
  1. Fixed logging - it is strongly recommended to take the latest!

    Now it logs only if g:ruby_debugger_debug_mode = 1. Otherwise, it
    doesn't write anything to the log file. It actually affects performance
    very very much, due to stupid implemenation of logging - to add one line
    to the log file, it reads whole the file to memory, add one line there,
    and then write whole file contents to the file back. Of course when the
    file is large, it will work very slow.
    
    So, enable debugging mode only if you have any issues with the debugger.
    And please pull the latest and update the plugin in your ~/.vim dir,
    because now it works much faster.
    Anton Astashov committed Feb 4, 2011
Commits on Jan 9, 2011
  1. Change hostname from 'localhost' to '127.0.0.1'

    According to users' feedbacks, sometimes the plugin doesn't work with
    'localhost' hostname with IPv6 configured. Replaced to 127.0.0.1, it
    should fix the issue.
    Anton Astashov committed Jan 9, 2011
  2. Add correct relative -> absolute path converter

    For the :Rdebugger command, added the relative -> absolute path
    converter. E.g. command :Rdebugger 'rackup config.ru' will be converted
    to "'/usr/bin/rackup' config.ru". First, it tries to find place of the
    script by 'which' command, if it is unsuccessful, then it assumes it is
    relative path with root dir = current dir.
    
    It also correctly works with spaces in directories, so Issue #37 is
    fixed.
    Anton Astashov committed Jan 9, 2011
Something went wrong with that request. Please try again.