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

[Thomas Dickey]

On Thu, Jun 02, 2016 at 03:13:03PM +0100, Chris Green wrote:
> On Thu, Jun 02, 2016 at 01:43:23PM +0100, Chris Green wrote:
> > On Thu, Jun 02, 2016 at 01:32:48PM +0100, Chris Green wrote:
> > > On Thu, Jun 02, 2016 at 08:26:30PM +1000, Brendan O'Dea wrote:
> > > > On 2 June 2016 at 19:03, Chris Green <address@hidden> wrote:
> > > > > I have installed the packages vile, vile-common and vile-filters and
> > > > > I've copied my customised vile.keywords over the default one in
> > > > > /usr/share/vile.
> > > > >
> > > > > The syntax highlighting colours stay stubbornly at the default, not my
> > > > > custom colours.  What have I missed? Is there something
> > > > > broken/different about how syntax highlighting is handled in 9.8l?
> > > > 
> > > > This works fine me with vile-9.8l on Ubuntu (which should be just a
> > > > binary rebuild of the Debian package).
> > > > 
> > > > Note: I didn't modify /usr/share/vile/vile.keywords, but copied it to
> > > > ~/.vile.keywords and edited that.
> > > > 
> > > > If you want to verify that you're picking up the correct file, try
> > > > running vile under strace:
> > > > 
> > > >   strace -etrace=file -o/tmp/t vile foo.c
> > > > 
> > > > then grep for vile.keywords in /tmp/t, which will show you which one
> > > > it is finding.
> > > > 
> > > Ah, oops, I'd changed VILE_STARTUP_PATH and hadn't added the default
> > > /usr/share/vile so it wasn't finding *any* vile.keywords.  The strace
> > > showed this up beautifully, thank you!
> > > 
> > However it seems as if I can't put multiple directories in
> > VILE_STARTUP_PATH, I tried the standard : separator as for PATH etc.
> > and what I see in the strace is:-
> > 
> >     stat("/home/chris/bin:/usr/share/vile", 0x6f4a60) = -1 ENOENT (No such 
> > file or directory)
> > 
> > Is there some way to specify multiple search paths in VILE_STARTUP_PATH?
> > 
> OK, I've worked around the problem.  I'm no longer setting VILE_STARTUP_PATH
> and I've done:-
>     export VILEINIT="source $HOME/bin/.vilerc"
> 
> Thus the compiled in VILE_STARTUP_PATH is unchanged (so files in
> /usr/share/vile are found) and I get my .vilerc from $HOME/bin.
> 
> 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...

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

signature.asc
Description: Digital signature