rdebug implementation for vim based on vim-addon-async
Vim script
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Note: try [1] first and only use this plugin if you can't get ruby-debug-ide to

minimal rdebug debugging support based on vim-addon-async.

- rspec/ruby will be suggested depending on whether the current file contains

- -rdebug is only suggseted as argument if the current file does not contain
  require "rdebug" to start the debugger.

  add require 'debug' to your ruby project, then run:
  AsyncRubyRDebug ruby file.rb

  Then you can use F5,F6, ... to step and set breakpoints
  (see plugin/vim-addon-rdebug.vim)

  You can pass input to debug process, see documentation of vim-addon-async

If something doesn't work contact me.

related work

github.com/MarcWeber/vim-addon-ruby-debug-ide [1]

https://github.com/astashov/vim-ruby-debugger (fails for me stepping 20 times)

There are some more debugger script at www.vim.org which work with any
commandline related debugger or can be extended to work with those.
I haven't tried them. Example:


  get github.com/MarcWeber/vim-addon-manager, and add 'vim-addon-rdebug' to the
  list of plugins to be activated on startup. Read its documention.
  It also talks about alternative and references Vim's help file about what the
  old way of installing plugins was.


  use any other way and install this plugin along with the plugins mentioned in
  the dependency section of ./addon-info.json (which all can be found on

    - no threading support yet
    - no support for debugging vars, but expecting vars by runing rdebug commands
      works (type text, visually select and hit <cr>), see vim-addon-async's
      documentation for details
    - if exception traces are logged vim sometimes interpretes them as "execution
      instruction" and jumps to that location.
      A simple F6 (next instruction) will take you back
    - probably this all is based on the wrong API - I should use what Eclipse,
      netbeans etc are using (ruby-debug?) - but it works for me.
    - sometimes a debug process seems to continue running with 100% CPU utilization.
      Kill it manually

support for multiple processes is started but not complete