On Wed, 3 Jan 2007, Mojca Miklavec wrote: > On 1/3/07, Hans Hagen wrote: > > Aditya Mahajan wrote: > > > We have another concern while calling the script. We need to call vim > > > using > > > > > > vim [options] -c "source path-to-script/2context.vim" filename > > > > > > This command is called using \externalprogram. We do not want to > > > hard code the location of path to the scirpt. Does it make sense to > > > add VIMINPUTS environment variable to texmfstart, to reduce the search > > > time? > > > > > hm, maybe but adding a truckload of editor paths will also slow down; an > > option is to add 'vim' as suffix someplace > > I don't think that using additional environmental variables makes sense > either. > > > but i wonder, isn't the vim stuff in the context tree? can kpse find it? > > > texmfstart --locate context.vim > > works OK on linux and returns the proper path to the vim script.
It works ok here also, but kpse: expansion is not working. Try texmfstart bin:vim kpse:core-ver.tex and texmfstart bin:vim kpse:2context.vim Aditya _______________________________________________ dev-context mailing list [email protected] http://www.ntg.nl/mailman/listinfo/dev-context
