Anatoli Sakhnik wrote:
Hi there!
I'm sorry having troubled you. I often type `vi' instead of `vim' for
brevity. Usually, I substitute the former of the system with a link to
vim, but this time I missed that fact (by the way, not for the first
time). So, there's no problem with linux compilation and running at
all.
OK. On RedHat and similar distros, "vi" is often the name of a Vim binary
compiled with "tiny" features only (no expression evaluation, no syntax
highlighting), and residing in /bin. If your /usr/local/bin is on the /
filesystem (not on a "mounted" partition), you may want to uninstall the
"vim-minimal" RPM package and have "vi" load your Vim 7.1 instead, e.g. as
follows:
rpm -ev vim-minimal
cd /usr/local/bin
ln -sv vim vi
An alternative would be to define "vi" as an alias for "vim -u NONE" (or maybe
"vim -u ~/.exrc") in one of your shell startup scripts, so invoking "vi" would
load Vim in "Vi mode". I guess this isn't what /you/ want but someone else might.
(The only reason for the existence of the vim-minimal package is in order that
you would still have an editor available when booting in single-user mode for
emergency repairs, without mounting any partition other than /).
Probably, I'll look at the problem with compilation under windows the
day after tomorrow if the problem won't have been solved by that time
(I have no possibility just at the moment at all).
-- Anatoli Sakhnik.
From what I've read in other threads of this mailing list, it looks like this
problem with gcc compiling on Windows might be solved soon by a 7.1a.002 patch.
Best regards,
Tony.
--
Oregano, n.:
The ancient Italian art of pizza folding.
