… with command-t
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.
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.
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.
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).
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)
…mand - huge thanks to edsono for the patch
…talled) - by gorkunov's request
…Log (per gorkunov's request)
…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)
+ruby, you won't be able to use double quotes in commands, e.g. :RdbEval "blabla". Now it is fixed.
… Vim for sending messages to ruby_debugger.rb. It should slightly improve performance.
…lease don't use previous commit at all. Thanks! :)
…allow its autoloading). Removed after.vim - moved its functionality to init script of before.vim. Now it should work with pathogen.
…d make starting of vim faster
…ption is raised, it will show exception message and jump to file/line of the exception. Usage: ':RdbCatch ExceptionName'.
…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).
…acktrace. You can jump to every backtrace item just double-clicking on it or pressing 'o'
…l variables are get when ruby_debugger.rb receives <breakpoint> or <suspend> responses. This way, we decrease number of requests to ruby_debugger.rb from two to one while jumping to breakpoint. This is our bottleneck, do you remember? :)