VIM Editor

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:

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.

A terminal/shell buffer script for python enabled [g]vim (+python).  Allows execution of shell commands in a vim buffer. It does not use r! <cmd>.   Some of it's features:       - It retains state because it's interactive.  For example, set an environment variable and it "stays" because the          shell process is the same through the whole session.       - It can run interactive line based programs like ftp/telnet/python/ssh/etc including masked password input (pty supported platform only).       - Since it's a vim buffer you can go into normal mode and move around the buffer, yank, paste, use word completion, etc       - Runs on Linux and Windows, primary development and testing is done on Linux.  Windows has limitations          ( no interactive programs ) due to lack of pty support.        Requirements: To use it you must have a python enabled [g]vim and run on a platform that supports pty ( i.e. Linux ), or pipes ( Windows, Linux, et all ). The pty version has much better formatted output than the pipes version and supports running interactive programs.  Please read vimsh.readme for other installation details.  Tested on vim 6.0 using Slackware and Gentoo Linux, FreeBSD, and Windows XP.   I'd also like to hear from users running other operating systems, i.e. QNX/Solaris/other BSDs. !!!!! WINDOWS USERS !!!!!, there is a zip file available at the above link. The version kept here on vimonline is a tarred, gzipped file ( tar.gz ). If you are going to use Winzip with the .tar.gz file be sure to turn off the "Tar file smart CR/LF handling". It doesn't work well. Please send me bug reports and suggestions if you use it.  I appreciate all the patches I've been getting lately!

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.

Nevertheless, spawning a shell in a VIM window is something I desperately sought after since the first day I started working with VIM, and searching on Google reveals that I'm not the only person. Someone even hacked together a Python script so you can start a shell in a window, but it's no terminal emulator, so your possibilities with this "shell" are limited. I wanted to have a real, working shell in VIM, so I wouldn't have to switch around with screen, use half-hearty solutions like splitvt etc.

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

mdb/

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/**

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:

" set 'updatetime' to 15 seconds when in insert mode au InsertEnter * let updaterestore=&updatetime | set updatetime=15000 au InsertLeave * let &updatetime=updaterestore

> Due to a repetitive stress injury, I have heavily customized the keys > in VIM. I don't know this is possible, but it would help there were an > automatic exit out of insert mode after a fixed idle duration. This > would save me having to hit the<ESC>  key so frequently to exit insert > mode. In other words, once in insert mode, after not hitting any keys > for 2 seconds or so, VIM would automatically take me out of insert > mode w/o me  having to hit the<ESC>  key. > I hope that made sense. > Thanks in advance         :au CursorHoldI * stopinsert will take you out of Insert mode when you don't type anything for 'updatetime' milliseconds (default 4000). To make it 2 seconds, add         :set ut=2000