Re: [vile] I can't get VILE_STARTUP_PATH to do what I expected it to do

[Chris Green]

On Thu, Jun 02, 2016 at 10:25:43AM +0200, Gary Jennejohn wrote:
> On Thu, 2 Jun 2016 09:12:39 +0100
> Chris Green <address@hidden> wrote:
> 
> > On Wed, Jun 01, 2016 at 07:38:22PM -0400, Thomas Dickey wrote:
> > > > 
> > > > This is all explained in the Invocation section of the vile :help
> > > > file.  VILE_STARTUP_PATH must be set in the confguration at compile
> > > > time.  
> > > 
> > > It's more flexible than that - VILE_STARTUP_PATH is an environment
> > > variable which overrides the compiled-in default for $startup-path
> > > 
> > > However, there are other things in the path, which you can see using
> > > 
> > >   2:which-source .vilerc
> > > 
> > > for example:
> > > --------------------------------------------------------------------------------
> > > Show which source-paths are tested for:
> > >   .vilerc
> > > ("*" marks found-files)
> > > 
> > > $cwd
> > >   .vilerc
> > > $HOME
> > > * /users/tom/.vilerc
> > > $startup-path
> > > * /users/tom/bin/.vilerc
> > >   /usr/share/vile/.vilerc
> > > --------------------------------------------------------------------------------
> > >   
> > I don't get *anything* like that!
> > 
> > When I do ':which-source .vilerc' I just see /home/chris/.vilerc
> > in the status line, and nothing else.
> > 
> > If I set VILE_STARTUP_PATH to /home/chris/bin then ':which-source
> > .vilerc' just produces .vilerc on the status line. ... or if I move to
> > another directory and run vile it gives /home/chris/.vilerc.  Setting
> > VILE_STARTUP_PATH doesn't seem to change anything.
> > 
> 
> I had the same problem, but if you enter it exactly as shown, with
> the 2:..., then all that stuff will show up.
> 
Ooh! So it does.  :-)   I was wondering what that '2' was about.

Thanls all, I seem to be sorted now.

-- 
Chris Green