On Mon, Jun 19, 2000 at 03:17:32PM +0100, Moore, Paul wrote:
>
> You shouldn't need to set environment variables or move files. If you do,
> there's a big bug in the vim packages (and I know there isn't in the
> versions I'm using - 5.6.070-1)
That's interesting, Paul.
I've done 3 Potato installs, two were fresh and one is an upgrade over
Slink. I've wound up setting the $VIMRUNTIME variable after each install.
However, I think this may be more of a secondary shell issue than a vim
issue. I noticed that after a clean setup, when vim is called from mutt,
it complains that it is unable to locate the syntax files. Setting the
variable fixes that problem here. I do recall vim being able to find
the syntax files if started from an XTerm. I also recall the problem
existing if mutt calls vim at the console as well, so it may well be
that the problem is how my ~/.bashrc file is configured as the trouble
occurs in a secondary shell. I start all my XTerms as login shells.
Thanks,
- Nate >>
--
Wireless | Amateur Radio Station N0NB | "None can love freedom
Internet | [EMAIL PROTECTED] | heartily, but good
Location | Wichita, Kansas USA EM17hs | men; the rest love not
Wichita area exams; ham radio; Linux info @ | freedom, but license."
http://www.qsl.net/n0nb/ | -- John Milton
