Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Vim most definitely can't "do everything" (Score 1) 246

by Miffe (#32160738) Attached to: Hacking Vim 7.2

My main peeve with vim is when it goes into "recording mode" or whatever that nonsense is, when I try to ":q" and hit something by mistake and the screen splits. I still don't know what I did wrong.

You entered q: which open the command line window.

And that vim always wants to go back to the last place in the file you edited, even if you edited the file ten years ago and really want to start at the top. The only way I found around that one is to make the .viminfo file chmod 000 so it can't save status.

There is a autocommand defined for this by default. Do a au! vimrcEx BufReadPost to disable it.

"A car is just a big purse on wheels." -- Johanna Reynolds

Working...