Group items tagged

The "Tag List" plugin is a source code browser plugin for Vim and provides an overview of the structure of source code files and allows you to efficiently browse through source code files for different programming languages.  You can visit the taglist plugin home page for more information

Change to the top level directory that contains your python source files, and do find -name '*.py' > cscope.files cscope -b

How can I work on VIM for python code such as cscope for C code?

to auto-indent a piece of code, highlight it in visual mode, and press =. To auto-indent the current line, press ==. Use gq to wrap the highlighted peice of text.

SuperTab: Makes all insert-mode completion done with tab. To use, simply press TAB while in edit mode. minibufexpl: Adds a buffer explorer to the top of Vim's window, simplifies working with buffers. taglist: A source code browser that works with many languages, including C/C++, Java, Python, Perl, PHP, ... vcscommand: SVN/CVS integration.

Applying substitutes to a visual block  tip karma   Rating 155/45, Viewed by 8082  Read and edit this tip on the Vim tip wiki. The wiki may have a more recent version of this tip. created:   March 28, 2001 8:26      complexity:   intermediate author:   Chip Campbell      as of Vim:   5.7 If you'd like to apply a substitute, or even any ex command, to a visual-block selected text region (ctrl-v and move), then you'll want Stefan Roemer's http://www.erols.com/astronaut/vim/vimscript/vis.vim .  Just source it in, and then press ":B".  On the command line you'll see :'<,'>BCtrl-V Just continue with the substitute or whatever... :'<,'>B s/abc/ABC/g and the substitute will be applied to just that block of text

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.

A guy I work with told me about a function that an old IBM text editor had that he said was useful, and that is to create folds in the file after a search such that every line that is visible contains the search pattern(except possibly the first). All lines that do not contain the search pattern are folded up to the last occurence of the pattern or the top of the file.  One use for such a function is to be able to make a quick and dirty api of a source file.  For example, if working in Java, you could run the function using the pattern "public|protected|private" and ithe results would be that only the method headers would be visible (well, close enough).  

This is a utility that performs a recursive diff on two directories and generate a diff "window".  Based on that window you can perform various diff operations such as opening two files in Vim's diff mode, copy the file or directory recursively to the other, or remove the directory tree from the source directory.