VIM Editor

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

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.

> I want to customize vimrc to change background color to yellow when switched to > "Insert mode".  It should be easy but I can not find how to do it. Any help will > be appreciated. > regards,   :au InsertEnter * hi Normal term=reverse ctermbg=darkgrey guibg=yellow   :au InsertLeave * hi Normal term=NONE    ctermbg=black    guibg=white Change to taste. see         :help InsertEnter         :help InsertLeave         :help :autocmd         :help :highlight

> 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

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

 "Give your most complex macros a name and store it for future recall and use" Problem statement(s): Can't remember those complex VIM macro sequences you use frequently?Wish you could save those macros beyond your immediate session? Wish you could share your VIM macros with each other? Why not templates as well in the same script?

>  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

You may have noticed that pasting outside text into Vim from insert mode can lead to awkwardly stair-stepped text. You may also know that this is easily avoidable via :set paste from normal mode. I paste from outside often enough, that I've added the following to my vimrc making it that much easier.set pastetoggle=<F5>

ERRCONDS = select.POLLHUP|select.POLLERR

This tip provides a (Windows only) means of using gvim as an external editor for almost any other program. This script has been tested with Lotus Notes and Internet Explorer on Windows NT.

> What's the way for pasting to command line? The usual way I use is    :put It's linewise, but there are some stunts (coming to mind: abusing :substitute and control+r to pull in content from various registers) It also takes a register, so if you want the system clipboard, you can do    :put * -tim

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>

is this possible: > :%s/\(.*\)/some_function(\1)/g > where some_function is something I would define myself. Python has this > function, BTW. > Thanks in advance.         :%s/.*/\=some_function(submatch(0))/ see         :help sub-replace-special         :help submatch() Note that since the * operator is greedy, .* matches the whole line, therefore the g flag doesn't change anything (there is only one whole line on each line).

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.

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:

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?

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

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

(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