\z1 ... \z9 */\z6* */\z7* */\z8* */\z9* *E66* *E67*
Matches the same string that was matched by the corresponding
sub-expression in a previous start pattern match.
I use Decho; its an instrumented-code type of debugging tool.
You can get the Decho plugin from:
http://vim.sourceforge.net/scripts/script.php?script_id=120
-or-
http://mysite.verizon.net/astronaut/vim/index.html#DECHO
(this latter one is always the most up-to-date)
To install if you're using vim7.1:
1. Install a new version of Decho:
vim Decho.vba.gz
:so %
:q
Regards,
Chip Campbell
>What is the best practice to have variable values being echod/written
>somewhere during execution which doens't impact the execution negatively?
Hyper-Linking to include files:
Place cursor over the file name (i.e. #include "fileABC.h")
Enter the letter combination: gf
(go to file)
This will load file fileABC.h into vim. Use the following entry in your ~/.vimrc file to define file paths. Change path to something appropriate if necessary.
"Recursively set the path of the project.set path=$PWD/**
This is the Vim cookbook page. It contains short recipes for doing
many simple and not so simple things in Vim. You should already
know the basics of Vim, however each command is explained in detail.
Each set of instructions is a complete package. Feel free to pick
and choose what you need.
File exploringAlright. You need two plugins, NERDTree and BufExplorer.NERDTree is started by typing :NERDTree and it will give you a much better file explorer than any other IDE. BufExplorer is started by typing \be and it will allow you to access a list of recently used files, and switch between them quickly.You might also want to bone up on windows and tabs (:help windows and :help tabs)
Following my thoughts yesterday, here are some VIM python scripts to add python breakpoint and debugging features to VIM. With this set up the F7 key will set a breakpoint on a line of code, Shift-F7 will remove all breakpoints and Shift-F12 will execute a script in the python debugger. This only runs on windows as far as I know, because it uses the 'start' command to launch the debugger in a seperate process without VIM waiting for it to finish. This allows you to look through the source code (and fix it) while the debugging is still in progress.
You're welcome. It turns out that it works if you set it like this:
set cdpath+=C:/Documents\\\ and\\\ Settings/rpdooling
or like this:
let &cdpath = ",,,C:/Documents\\ and\\ Settings/rpdooling
I don't understand why and I'm trying to find out from the vim
mailing list, which is where that solution came from.
Regards,
Gary