interesting parallel problem I've been having that this just fixed. I
never get this behaviour normally from vim on the command line.
However, when I set up mutt with
set editor = "vim -u .mutt/vimrc"
having previously had
set editor = "vim"
I started to get the behaviour being described above. I tried
set editor = "vim -N -u .mutt/vimrc"
and it has returned to normal. My normal .vimrc which it would've been
using previously consists of only
I've no real problem cos it's wokring, but there's definitely something odd
about what circumstances vim behaves more like vi. Either that or the
keymap gets a wee bit screwed up or something?
On Tue, 11 Sep 2001, Aidan Kehoe wrote:
>> > The -N isn't necessary, but just makes vim less vi-like and more
> > userfriendly.
>> Someone doesn't get the point of vi :-) .
> `... when the elephant man broke strong men's necks, when he'd had too
> many Powers, ...'
> Irish Linux Users' Group: ilug at linux.ie>http://www.linux.ie/mailman/listinfo/ilug for (un)subscription information.
> List maintainer: listmaster at linux.ie
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!