VIM Editor

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:

The GVim Portable Launcher allows you to run GVim from a removable drive whose letter changes as you move it to another computer. The program can be entirely self-contained on the drive and then used on any Microsoft Windows computer.

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.

Applying substitutes to a visual block

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.

If a file type you want to use is not detected, then there are two ways to add it.

MARVIM - MAcro Repository for VIM "Give your most complex macros a name and store it for future recall and use"

mdb/

> Hello,  Is there a way to hilight different portions of statusline > using different colors? Thanks!

Cursor line and more... * You can turn on cursor line and cursor columns ':set cursorline' ':set cursorcolumn'

* Pressing 'q:' or ':<Ctrl-f>' gives the command history window (list of previously executed commands in the current session) * Pressing 'q/' or '/<Ctrl-f>' gives the command history window (list of previously executed commands in the current session)

Note: to highlight special keywords we can use the match option as ':hi <MyGroup> ctermbg=red' ':mat <MyGroup> /<pattern>/' To clear these highlights do ':mat[ch]'

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 "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

Vim already maintains a list of numbered registers containing the last 9 deletes.  These previous deletes can be referenced using [register]p, so "1p will paste the last delete, "2p the 2nd last delete.  For more information see |quote_number|. Vim does not provide any mechanism to reference previous yanked text.  In Emacs this feature is called the "kill ring".

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.

Clewn implements full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc.

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.

Here's a little Vim trick that might be of interest. If you're on a non-Windows machine, you can make the Vim hardcopy command print to a postscript file instead of a real printer. Try issue the following::hardcopy > file.ps

Flydiff is a Vim plugin to perform on-the-fly diff on the current buffer with some version control system and show the differences in another buffer.

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!