Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master

Aug 14, 2011

  1. Update final files (autoload/ruby_debugger.vim)

    Anton Astashov authored
  2. Merge pull request #55 from stephenprater/efficient_logging

    efficient logging
    Anton Astashov authored

Aug 13, 2011

  1. change writing strategy to match vims.

    A.G. Russell Knives authored

Aug 11, 2011

  1. spaces solved

    A.G. Russell Knives authored

Aug 08, 2011

  1. efficient logging

    A.G. Russell Knives authored

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 authored

Jul 05, 2011

  1. Fix getting absolute path

    Anton Astashov authored

May 01, 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 authored

Apr 30, 2011

  1. Merge pull request #46 from rweng/master.

    It really works, thanks, rweng.
    Anton Astashov authored

Apr 06, 2011

  1. Robin Wenglewski

    fix 'too many file names'

    rweng authored

Feb 05, 2011

  1. Update README and the plugin's help file.

    Anton Astashov authored
  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 authored

Feb 03, 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 authored

Jan 09, 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 authored
  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 authored
  3. Improve logging - messaging and Server/Breakpoint classes

    Added very detailed logging of messages from/to rdebug-ide and
    ruby_debugger.rb and detailed logging of the :Rdebugger command and
    toggling breakpoints. They are things which often don't work, so such
    detailed logging will help to find/fix user's issues related to the
    vim-ruby-debugger plugin.
    
    To enable detailed logging, you need to enable debug_mode. For this,
    add
    
      let g:ruby_debugger_debug_mode = 1
    
    to your .vimrc. It will log to the ruby_debugger_log file (as before).
    Anton Astashov authored
  4. Fix crash when there are too long variable values

    Sometimes when you have too long variable values (e.g. if you use
    Nokogiri objects, they will display their full XML contents in the
    variable value. Imagine you received 300kB of an XML response and you are
    trying to watch the Nokogiri::XML object :)). Vim built-in regexp
    parser raises errors on very long strings and crashes whole Vim.
    To avoid it, now the plugin truncates too long variables (> 30000
    chars)
    Anton Astashov authored

Oct 02, 2010

  1. Added expanding of relative pathes to absolute path in :Rdebugger com…

    …mand - huge thanks to edsono for the patch
    Anton Astashov authored
  2. Whoops - forgot to add documentation about automatic running :AnsiEsc…

    …... Added.
    Anton Astashov authored
  3. Added automatic colorizing of :RdbLog by AnsiEsc plugin (if it is ins…

    …talled) - by gorkunov's request
    Anton Astashov authored
  4. Added default options 'setlocal wrap' and 'setlocal nonumber' to :Rdb…

    …Log (per gorkunov's request)
    Anton Astashov authored
  5. Added global variable g:ruby_debugger_builtin_sender for disabling se…

    …nding messages to debugger by built-in Vim Ruby interface (if it is compiled +ruby). It is because built-in Ruby doesn't work for some users (dunno why)
    Anton Astashov authored

Sep 07, 2010

  1. Fixed bug with escaping of double quotes - if your VIM is compiled with

    +ruby, you won't be able to use double quotes in commands, e.g. :RdbEval
    "blabla". Now it is fixed.
    Anton Astashov authored

Sep 01, 2010

  1. Added :RdbLog command for watching standard output of executing Ruby …

    …scripts
    Anton Astashov authored

Aug 30, 2010

  1. If vim compiled with +ruby, added using of Ruby interface built-in to…

    … Vim for sending messages to ruby_debugger.rb. It should slightly improve performance.
    Anton Astashov authored

Aug 25, 2010

  1. Added instructions how to use debugger with Ruby 1.9 and Rails 3 to d…

    …oc file
    Anton Astashov authored

Aug 17, 2010

  1. Fixed errors of previous commit. Now it really works with pathogen. P…

    …lease don't use previous commit at all. Thanks! :)
    Anton Astashov authored

Aug 15, 2010

  1. Fixed tests. Renamed ruby_debugger_test.vim to ruby_debugger.vim (to …

    …allow its autoloading). Removed after.vim - moved its functionality to init script of before.vim. Now it should work with pathogen.
    Anton Astashov authored
  2. Moved all code of the plugin to autoload dir. Theoretically, it shoul…

    …d make starting of vim faster
    Anton Astashov authored

Nov 06, 2009

  1. Fixed tests

    Anton Astashov authored
  2. Added documentation for :RdbCatch to vim-ruby-debugger help file

    Anton Astashov authored
  3. Added tests for exceptions catcher

    Anton Astashov authored
  4. Added :RdbCatch command. It allows to set exception catchers, if exce…

    …ption is raised, it will show exception message and jump to file/line of the exception. Usage: ':RdbCatch ExceptionName'.
    Anton Astashov authored

Nov 05, 2009

  1. Added conditional breakpoints. For setting condition to the breakpoin…

    …t, move cursor on the set breakpoint and type :RdbCond condition, where condition is any ruby expression, e.g. current_user.id == 1. Conditions are displayed in the Breakpoints Window (if they are set, of course).
    Anton Astashov authored

Nov 03, 2009

  1. Added tests to backtrace functionality

    Anton Astashov authored
Something went wrong with that request. Please try again.