On Tuesday, 6 May 2014 19:33:02 UTC+1, Charles Campbell wrote: > Graham Nicholls wrote: > > > On Tuesday, 6 May 2014 12:18:39 UTC+1, 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. > > > Seems like it's nocompatible which is doing it - by a process of > > elimination - I started at the bottom, eliminating lines/functions till it > > worked. > > > > > > All very odd, but thanks for your help. > > > > > I'm not sure that you've correctly identified the problem. I've > > attached two files: > > > > nicholls : a shell script that runs vim a hundred times, using > > nicholls.vimrc (which I copied from your earlier email) and which > > immediately tells vim to quit. I also ran it after having changed vim > > to gvim, by the way. > > > > Result: a bit of blinking as (g)vim popped in and out, but otherwise it > > ran as expected. If a vim had refused to quit, a (g)vim window would > > have remained open. I did this on a scientific linux 6.4 (Carbon) > > system with a huge vim 7.4.272. > > > > Suggestion: try running vim with -V and, when it refuses to quit and > > goes insert instead, maybe you can see what happened. I don't much like > > having distributed .vimrc files, as that frequently causes problems, but > > I don't see anything in that .virc that should cause that quitting > > issue. Dropping the "set nocompatible" is like preventing yourself from > > having a car accident by removing the car's battery. It may work but > > one does miss out on a lot. > > > > What happens when you run the attached script? > > > > Regards, > > Chip Campbell
100 iterations with no windows left open , interestingly. I'd agree that I've not identified the problem; just a temporary fix, and running with compatible set _is_ a non-starter. In fact, it wouldn't be running, it'd be hopping. I wonder if it's somehow about how fast it's typed. I could run up something in expect to slowly type :q! and see if that exhibits the problem, if I get the time. Thanks for your script, but seriously, ksh, not bash? :-) -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
