Group items tagged

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.

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

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

This script provides many useful utility functions for buffers, windows and other misc things. I needed a place to share all the misc. utility functions so I renamed bufNwinUtils.vim and started adding these additional functions. I intend to create/collect many more useful functions and add to this script.

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)

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!

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.

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

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:

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.

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.