Friday, December 9, 2011

How can I keep vim from keeping context

I've been annoyed by it for years, but maybe it has become more
aggressive.

I *HATE* colors because I cannot read blue on black or yellow on
white.
Those colors are all too common.

I *HATE* finding myself in the middle of a file because several months
ago I
edited the same file and that is where I left off.

VIM is waaaay too smart for its own good.

Yesterday, I googled the answer to shutting down VIM's memory:

set viminfo='0,:0,<0,@0,f0,/0'

cool except that vim responded with, "I saw that in your vimrc file,
and
I do know what you want to do, but I am not going to honor it because
you left off something or other (and I won't tell you what)."

OK, not quite true, but this is true:

> Error detected while processing /old-home/bkorb/.vimrc:
> line 39:
> E527: Missing comma: viminfo='0,:0,<0,@0,f0,/0'
> Press ENTER or type command to continue

and adding a comma yields another error and fixing that goes back to
this.
Entirely equivalent to "I won't tell you what."

Morals to the story:

1. Clear error messages are crucial
2. How do I tell VIM that I want it to be a stupid (non-fancy) text
editor?

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