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

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:

mproves over standard matchparen.vim plugin by echoing line containing matching bracket in the status line so you can quickly see which block is terminated by this paren.  Also scans for braces/parens which are off-screen.

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.

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.

>  I was wondering if there's any debugger written specifically for Vim >  code?   I've got a thorny problem on a vim plugin on Solaris (I can't >  share the code) and stepping through the code would be lovely (though I >  realize this could be difficult, given the nature of vim). As I am sure you found out from Tony's post Vim has a built in debugger for Vim scripts. What I would suggest to you is to download and use this plugin by Hari: " BreakPts - Debug Vim Scripts " Author: Hari Krishna Dara " http://www.vim.org/scripts/script.php?script_id=618 I use it regularly and love it. HTH, Dave

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?

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

Vim Outliner is a vim plugin that turns the powerful vim editor into a powerful outliner of the likes of GrandView, More and MaxThink. It is keyboarder friendly and very fast. If you can touchtype, you can outline as fast as you think.

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)

You can refer to the "Finding unused keys" section in the "Mapping keys in Vim" tutorial available at: http://vim.wikia.com/wiki/Mapping_keys_in_Vim_-_Tutorial_%28Part_2%29

eta keys are almost always safe (<M-A>, <M-B>, etc.). Check for mappings from plugins, etc. before using. When in doubt, use the help. For example, to see if CTRL-J is taken (it is, but there are several commands to do the same thing) type :help CTRL-J and then press CTRL-D instead of ENTER to list all results. Then view each result to see what they do and if there are any alternate ways to do the same thing before mapping. If the mapping is for one mode only, you can prepend the mode. For example, for CTRL-J in insert mode, :help i_CTRL-J

Oh, and you can also use the map leader (see :help <Leader>), which defaults to the backslash key. For example, nmap <leader>h :echo "hello world!"<CR>