118 reputation
4
bio website
location
age
visits member for 1 year, 7 months
seen Feb 24 at 15:22

Oct
31
comment Changing gVim behaviour on Red Hat
@slm - BTW, if your TRS-80 was the CoCo, then you may be familiar with the DRAGON 64.
Oct
31
comment Changing gVim behaviour on Red Hat
@slm - not trying to be argumentative here, but I never said that your spelling was incorrect. Not being a native English speaker gives me the freedom to choose my preferred spelling style. I just happen to like some British spelling more (behaviour, colour). I guess the fact that my 1st home computer was from UK, gave me some bias here... I might be wrong but I don't remember reading an SE preference in the FAQs. Thanks for some of your corrections that I did accept :-)
Oct
30
revised Changing gVim behaviour on Red Hat
edited body
Oct
30
comment Changing gVim behaviour on Red Hat
A-ha... so nocp probably changed a few more variables that I did not list. I wish one could print out the :se all screen, so I could compare values in both cases.
Oct
30
awarded  Editor
Oct
30
revised Changing gVim behaviour on Red Hat
"gVim", "GVim" and "gvim" are all used in the docs. "Vi" is the only form there. "Behaviour" is a leggit word.
Oct
30
awarded  Scholar
Oct
30
accepted Changing gVim behaviour on Red Hat
Oct
30
comment Changing gVim behaviour on Red Hat
Any idea why? The configuration variables have the same values?!
Oct
30
comment Changing gVim behaviour on Red Hat
However (!) renaming my .gvimrc to .vimrc seems to solve the two problems!
Oct
30
comment Changing gVim behaviour on Red Hat
Thanks, but... I listed the (what I think to be the) relevant variables in the question itself, and you can see that it is set to nocompatible.
Oct
30
awarded  Student
Oct
30
asked Changing gVim behaviour on Red Hat
Oct
9
awarded  Supporter