This is a continuation of vimscript #182 by Gergely Kontra, who has asked me to take over support and maintenance.  So if you have any questions or suggestions, please direct them to me.  Please read the description below as some enhancements have been made as well. Description:   This script allows you to use the tab key to do all your insert   completion (:help ins-completion).   Ex. To complete the word bar or baz     foo bar baz     b<Tab>   This version of SuperTab supports several configuration options:   NOTE: Please see the "Global Variables" fold in the script for more details.   - The default completion type (defaults to keyword completion)   - The duration that a non-default completion type will be retained before     switching back to the default (defaults to retaining the current     completion type until you manually kick off a different one).   - Disabling of mid-word (word character to the left and right) completion     (defaults to mid-word completion enabled).   - Ability to change the default mapping to kick off forward or backward     completion (defaults to <tab> and <s-tab>).   - A discovery list to determine the default completion type to use for any     given buffer (defaults to no discovery).   - Option to highlight the first entry in the results if your completeopt has     'menu' and 'longest'.

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.

Tired of debugging Python using print statements? Don't like the cumbersome PDB (Python debugger) console? Prefer using Vim for coding your Python programs? VimPdb is the solution - allows debugging Python in an IDE-fashion, right within the Vim editor.

(requires vim7.0aa snapshot #188 or later) DrChip's cscope interface supports commands:     CS     [cdefgist]   : cscope     CSl[!] [cdefgist]   : locallist style (! restores efm)     CSs[!] [cdefgist]   : split window and use cscope     !            split vertically     c (calls)    find functions calling function under cursor     d (called)   find functions called by function under cursor     e (egrep)    egrep search for the word under cursor     f (file)     open the file named under cursor     g (global)   find global definition(s) of word under cursor     i (includes) find files that #include file named under cursor     s (symbol)   find all references to the word under cursor     t (text)     find all instances of the word under cursor

The grep plugin integrates the grep, fgrep, egrep, and agrep tools with Vim and allows you to search for a pattern in one or more files and jump to them. To use this plugin, you need the grep, fgrep, egrep, agrep, find and xargs utilities. These tools are present in most of the Unix installations. For MS-Windows systems, you can download the GNU grep and find utilities from the following sites:

description Several modern GUI editors list your open buffers as tabs along the top or bottom of your screen (VisualStudio, DreamWeaver, EditPlus and UltraEdit come to mind), now we have this feature in VIM! You can checkout a screenshot here: http://www.wavell.net/vim/vim_screenshot.gif. You can quickly switch buffers by double-clicking the appropriate "tab" (if you don't want to use the mouse just put the cursor on the "tab" and press enter). As you open and close buffers the tabs get updated. Buffers that are modified get visually marked and buffers that are open in a window get visually marked. The -MiniBufferExplorer- opens automatically when you open more than one eligible buffer (no need to open the explorer if you’re only editing one file.) -MiniBufExplorer- doesn't bother showing non-modifiable or hidden buffers. You can delete buffers by selecting them and pressing d on the keyboard.

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?

lets you embed options in the file itself so that other people who edit the file in vim will see it the way you do—all the tabs will line up correctly, etc., regardless of how they have their ~/.vimrc file set up. This is called a modeline, in the parlance of our times.

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

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?

In visual mode, / and ? will update the visual selection just like any other cursor-movement command. In order to actually search within the visual selection, you will need to use the \%V atom, or use the markers defined by the visual selection with \%>'< and \%<'> atoms. This is best done by leaving the visual selection with <esc> before entering your search. You may want to consider a mapping to automatically leave visual selection and enter the appropriate atom(s). For example:

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).  

The Wildmenu The best vim feature is the wildmenu. Add a set wildmenu to your vimrc and discover the possibilities of filesystem surfing ^^ Enter :e in the command line and press ^D. Vim will show you all possibitilites in a nice little window. By entering the start of a filename and pressing tab it completes for you then. If it was a folder you can now press ^D again to get the contents. Once you finished the command this window will disappear again and you can continue working. Works of course for all commands not only the open command.