Re: Odd behaviour with :q!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCgAGBQJTaN0iAAoJEERGtGilKM7wnYAH/25XLWxMpdLgW/bAf/F0+7dd
H7MBJTyagjEmKPe5pSEZoPN7FcuWyP+r987ZHdRpAzDAcbgAZgGKypkeZGvebTIC
tkB0DlXdbOuX8uIYZ6TTJExERHpUxcsyNwqXT6pKD0FfBgeHpcB46i8iM6lsyUx/
s4eGI8l3no3ROs/4nhOIIhyRiqIvth0kUaaeu9lzivA3ECJmTWe9fgnGCGwiRUOS
qqRuAO4KECdBEKb5/FBhzzEQKpOLnl9uf5xm/nsegbjEUwNpd6YEFAramGxB8pla
rqb5EloI5vupZi4Mu9tcAmrGt6AedGKPTTYkcvB3khGxsMWzSk3l62za9UMaxJE=
=Lwrx
-----END PGP SIGNATURE-----
On 2014-05-06 04:18, Graham Nicholls wrote:
> On a RHEL 6.2 server, I get odd behaviour with vim 7.2.411;
> randomly at a frequency of about 1 in 5, entering :q! (when in
> command mode) puts me into insert mode after adding an M and a
> blank line.
>
> A subsequent :q! usually works, but sometimes does the same.
>
> I'm using konsole under KDE if that's of interest.

It would be more helpful to know what plugins and non-standard
settings you have. I'm going to guess that if you repeatedly try

vim -u NONE ...

it shouldn't give you any trouble. If it does, then there's
something much shadier going on. If that works just fine, there's
likely some mapping interfering with your command.

I also presume that, if you type ":q!" in other programs, such as
another text-editor or the command-shell, you have no problems
(ruling out a flaky keyboard like the built-in one on my laptop here
where the ZAQ1!<tab> cluster is broken).

-tim