dave--uk wrote:
In the end I found the problem - and this did help, but not as I expected.
It was actually in /etc/profile.d/vim.*. If the uid100 vi is aliased
to vim (so I get all the nice features) otherwise it's not and I dont.
That's why I sometimes got the nice stuff and sometimes didn't.
Yakov Lerner wrote:
On 7/10/06, dave--uk [EMAIL PROTECTED] wrote:
2) when i edited a file, vim remembered the last position I was at
For this to work, you need certain definitions in your ~/.vimrc.
1) You need some definition for 'viminfo' option, for example:
set
Do not have too much faith in RH. Several years ago, they included
an alpha version of vim (6.0z, I think) in their release, and linked it
to /bin/vi (or maybe /usr/bin/vi ). The last time I checked, the system
vimrc file they included was seriously crufty.
Have a look at the system
In the end I found the problem - and this did help, but not as I expected.
It was actually in /etc/profile.d/vim.*. If the uid100 vi is aliased
to vim (so I get all the nice features) otherwise it's not and I dont.
That's why I sometimes got the nice stuff and sometimes didn't. RH9
did a
I'm not really convinced that is the problem. Nothing really points to it.
1) Syntax highlighting does work for some files - if it was the build
it wouldn't work at all.
2) Not remembering the file positions sounds like a configuration switch.
3) The help files being opened binary, rather than
I used to use RH9 and was VERY happy with three features of vim (6.1.320)
1) almost everything was syntax highlighted, including, for example, httpd.conf.
2) when i edited a file, vim remembered the last position I was at
3) the help worked
Having moved to Centos-4 (RHEL) (vim 6.3.046) none of
On 7/10/06, dave--uk [EMAIL PROTECTED] wrote:
I used to use RH9 and was VERY happy with three features of vim (6.1.320)
1) almost everything was syntax highlighted, including, for example, httpd.conf.
2) when i edited a file, vim remembered the last position I was at
3) the help worked
Having
