This vim plugin provides a debugger interface to DBGp protocol, and therefore Xdebug (only tested on Xdebug 2).
- Open the whole debugger session in a new tab, so that your carefully configured windows don't get messed up. When you end the session the whole tab closes.
- The watch window now clears each time a new request is made, so that it doesn't get confusing.
- Do a quick eval on expressions in visual selection.
- If the maximum depth is reached on an array or object in the watch window, hit
<CR>(return key) and the contents will be inserted inline.
- Better code folding in the watch window.
- You can now show all globals in the current context, and class variables (i.e. static variables).
- Better information and error messages.
- Improved formatting for eval results in watch window.
- Fixed some problems with unicode.
- The default depth of data to retrieve is now configurable, so that you can look deeper into arrays/objects.
- A new "command" window shows the list of commands made to the debugger, and you can hit
<CR>on any of them to re-run it. You can also type in commands and
<CR>will execute them.
- When the debugger session ends, no longer do you get an ugly exception. Instead, you get a nice message telling you that it's closed.
- Windows are better arranged (I think).
- Toggle variable for putting it in debug/verbose mode.
- Vim compiled with Python (2) support
- DBGp protocol enabled debugging module, such as Xdebug.
Clone or download a tarball of the plugin and move its content in your
~/.vim/plugins/ directory should now have two more files:
Using git and Pathogen
Clone this repository in your
~/.vim/bundle directory (and yeah, you're done).
Add this to your
Then, from the command line, run:
vim +BundleInstall +qall
- setup Xdebug - or other DBGp enabled server - correctly (with proper remote debug option)
F5to make Vim wait for a debugging connection and browse your PHP file (it will wait for 30 seconds, to give you plenty of time to run your program).
All the currently opened windows will be closed and debugging interface will appear.
Once in debugging mode, the following mappings are available:
<F1>: set breakpoint
<F2>: step into
<F3>: step over
<F4>: step out
<F6>: stop debugging
<F11>: shows all variables
<F12>: shows variable on current cursor
,e: evaluate an expression and display the result
- To stop debugging, press
- Jon Cairns
- Ludovic Pelle
- Kévin Gomez
- Sam Ghods
- Seung Woo Shin
The MIT/Expat licence.