Disappointingly, over here it doesn't work with two backslashes, only
with one. Possibly because there are two texmf.cnf (minimal linux
distro) which give different answers:
./texmf/web2c/texmf.cnf, which claims
% A place for local additions to a standard texmf tree.
% This tree is not used for
Johan Sandblom wrote:
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
My suggestion would be:
run(--expand-path='$#{varname}')
Taco
Yes, that works.
Johan
2006/9/17, Taco Hoekwater [EMAIL PROTECTED]:
Johan Sandblom wrote:
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
My suggestion
Taco Hoekwater wrote:
Johan Sandblom wrote:
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
My suggestion would be:
Attempting to find out why this happened on linux
~$ texmfstart ctxtools --updatecontext
CtxTools | updating
CtxTools | unable to change to
I found that line 114 of kpse.rb can be changed from
path = run(--expand-path=\\\$#{varname}) rescue ''
to
path = run(--expand-path=\$#{varname}) rescue
path = run(--expand-path=\\\$#{varname}) rescue ''
to
path = run(--expand-path=\$#{varname}) rescue ''
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
so
