Wednesday, September 8, 2010

Re: Dealing with viminfo overwriting? -> :set vi=n..

* Benjamin R. Haskell <vim@benizi.com> [2010-09-08 16:36]:
> It's only within the last few years that Vim has become my main editor.

(but apparently not for edting emails..
you can tell by the trailing spaces ;-)

> Now that I tend to use many vim instances at a time, I'm finding it
> frustrating that I'm losing much of my command history due to firing
> up 'temporary' sessions that overwrite more useful history. A
> feature of Zsh that I really love is INC_APPEND_HISTORY, where
> history items are appended into history as soon as they're entered,
> instead of appending the whole shell session's history upon exiting.
> Is there any similar capability for viminfo?

no.. vim does not have an option for "merging" of viminfo files.

> How does everyone here deal with this kind of problem?

tell vim to write its info into separate viminfo files.

you could start vim from different directories
which have their own vimrc, directing it
to use a special (local) viminfo file, eg:

:set vi=n.viminfo
:set vi=n~/.vim/viminfo.foo

i had been thinking about this for
over a decade now.. but all solutions
seem to have been too hard to handle. ;)

Sven

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments:

Post a Comment