Re: [vile] Problem with syntax highlighting in vile 9.8l

[Thomas Dickey]

----- Original Message -----
| From: "Chris Green" <address@hidden>
| To: address@hidden
| Sent: Friday, June 3, 2016 4:49:44 AM
| Subject: Re: [vile] Problem with syntax highlighting in vile 9.8l
| 
| > > 
| > > However, an enhancement request, can we have a $PATH type
| > > VILE_STARTUP_PATH
| > > please.  It would mean that custom versions of vile
| > > initialisation
| > 
| > sure - it's simply been overlooked.
| > 
| > > files could be added as needed in a local directory and wouldn't
| > > be
| > > lost when upgrading.
| > > 
| > > For example, it would be possible to set VILE_STARTUP_PATH to
| > > something like $HOME/.vileconfig.  Your .vilerc would be in that
| > 
| > VILE_STARTUP_FILE does that...
| 
| Does it?  That's not how it reads in the man page, it says:-
| 
|        VILE_STARTUP_FILE
|               Override  the name of the startup file, normally
|               ``.vilerc'' (or ``vile.rc''
|               for non-UNIX systems).
| 
| That suggests to me that setting VILE_STARTUP_FILE would allow me to
| use .MyVilerc as a startup file instead of .vilerc but wouldn't
| change
| the directories searched to find it.

yes - it's not obvious from the (terse) description, but setting it to a full 
pathname
does work (I tested that last night, to refresh my memory).

...I've got some documentation and testing left on my xterm work, will be back 
on vile next :-)

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net