Tag Info

The first place to check is if there's a backport, but there isn't, which isn't surprising since maverick has vim 7.2 too. The next thing to try is if someone's put up a repository with vim 7.3 packages somewhere, preferably a PPA. There are many PPAs with vim, including several with 7.3 (not an exhaustive list). If you don't find a binary package anywhere ...

vim has an event you can bind to for this, FocusGained, combine this with the redraw! command (the ! causes the window to be cleared first) :au FocusGained * :redraw! The syntax here can be read as 'automatically run the command (au is short for autocmd) :redraw! when I get the event FocusGained for any file matching the pattern *'. to make this ...

First of all, quick naming correction - anything open in Vim is a "buffer". The terminology here is similar to emacs, if you are familiar with that editor. Buffers simply refer to open files in the memory of the current Vim process. To see a list of you buffers, use :ls which shows you a list of the current buffers, numbered in the order that they were ...

The colours of vim-powerline should be located in your .vim directory. If you use a plugin manager it may be .vim/bundle/ followed by the vim-powerline/autoload/Powerline/Colorschemes tree. The file you are looking for should be the default.vim. The colour setting you are looking for is : . \ Pl#Hi#Segments(['mode_indicator'], {¬ . . \ 'n': ...

Install both and try them both, they use the same configuration etc. so there's no risk. As far as differences are concerned: one is a graphical tool one is a command line tool. So the advantage of vim to gvim is that you can use it easily over an ssh connection. (You can do the same with gvim by tunneling X but that has quite some overhead.

I got all the pieces together to do the trick. The best way is to create a custom mapping for all the commands: map <F8> :let mycurf=expand("<cfile>")<cr><c-w> w :execute("e ".mycurf)<cr><c-w>p Explanation: map <F8> maps on "F8" the commands that follow let mycurf=expand("<cfile>") gets the filename ...

After doing these commands: cd ~/.vim/bundle git clone git://github.com/mattn/calendar-vim You need to add the following line to your $HOME/.vimrc file: Bundle 'calendar-vim' After doing this when I start up vim I get the command: :Calendar Which shows the following in vim. screenshot ...

Usually people want it the other way around, using (approximated) colors defined in a GVIM color scheme in the console, too. It all depends on your colorscheme; it provides the attributes (like bold / italic), foreground and background colors for terminals, color terminals, and the GUI. Good color schemes provide similar definitions for all three. You can ...

The command should be "gvim --remote-tab file1 [file2 ...]". If no instance of gvim is running, it produces an error message (which you won't see if you're not launching it from a terminal anyway) and does what you say. This command might not work as expected if you open two different gvim windows and then close the first one (instead of opening new tabes ...

gvim package shall have all vim coming along. Meaning, if you wish to fall back to vanilla vim you can. Anyway, the biggest difference IMO is that vim depends on the terminal to handle special characters and key-sequences. If you wish to map and exploit things like <c-space>, <m-ins>, ... just forget about it with vim. Of course gvim has menus, ...

Did you install the GTK2 '-dev' packages? They're the 'other half'. Most people usually just need the libraries, since the programs are already written and compiled, they just link to the libraries and life is good. But people compiling code need the 'descriptions and pointers' to the library routines, which is contained in the '-dev' packages. I write ...

You could look into the Teledactyl add-on for Thunderbird from 5digits.org. They produce a Pentadactyl add-on for firefox which works nicely for controls, although text boxes are admittedly un-vim-ish. Feature-list says it supports external editors, so gvim could be in your future.

This happens to me as well. The workaround that I use is to minimize gVim then maximize it again. After that the status bar is visible again. Bug is described here: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/137854 Bug is reported fixed in debian, but the issue is still there with Ubuntu 11.04 (Natty)

See :tabnew and :tabedit in :help tabpage. (I'm not sure if you can (or want to) re-map :edit) (Edit There is a related and helpful SO discussion) (Edit to match your refined question) I doubt it will be less hassle than alias gvim=gvim -p, but using autocmd (and some Vimscript, everything in your .vimrc) this might be possible. (But I'm not knowledgeable ...

You might try vimoutliner, a vim plugin: http://www.vim.org/scripts/script.php?script_id=3515; I haven't used it myself (don't really use an outliner), but it's easy to install and seems to be to use.