Re: Understanding expansion of TEXMFHOME
- From: Christian Mandel <c.mandel@xxxxxxx>
- Date: Tue, 16 Sep 2008 14:11:50 +0200
Enrico Gregorio schrieb:
Christian Mandel <c.mandel@xxxxxxx> wrote:
Hello,
I wonder how to get a second TDS tree in my home directory (properly). I
have a working solution, but I dont't understand why it behaves like it
does and maybe there's a better way ...
I use TeXLive 2008, and I have put the line
TEXMFHOME = ~/texmf,~/texmf-pub
in /usr/local/texlive/2008/texm.cnf. This works, but when doing
kpsexpand '$TEXMFHOME'
i get the answer
/home/chris/texmf,~/texmf-pub
so the first time the path gets expanded, the second time it doesn't.
Can that fact cause problems? Is this the right way to get a second TDS
tree in the home directory?
I need this, because one of the trees holds private files like .lco
(letter customization for KOMA-Script) and similar things (being under
version control), the second tree holds packages not shipped with
TeXLive (e. g. the cvs version of pgf/TikZ and bibLaTeX).
The separator should be a colon or a semicolon, not a comma.
You are right (if I understand the manual right), but that does not
change the odd behaviour of the expansion. Now,
kpsexpand '$TEXMFHOME'
leads to
/home/chris/texmf:~/texmf-pub
and
kpsexpand '$TEXMF'
to
{/home/chris/.texlive2008/texmf-config, \
/home/chris/.texlive2008/texmf-var,/home/chris/texmf:~/texmf-pub, \
!!/usr/local/texlive/2008/texmf-config, ...
Thanks, Chris
.
- Follow-Ups:
- Re: Understanding expansion of TEXMFHOME
- From: Enrico Gregorio
- Re: Understanding expansion of TEXMFHOME
- References:
- Understanding expansion of TEXMFHOME
- From: Christian Mandel
- Re: Understanding expansion of TEXMFHOME
- From: Enrico Gregorio
- Understanding expansion of TEXMFHOME
- Prev by Date: \pdftexversion in XeTeX
- Next by Date: Re: Understanding expansion of TEXMFHOME
- Previous by thread: Re: Understanding expansion of TEXMFHOME
- Next by thread: Re: Understanding expansion of TEXMFHOME
- Index(es):
Relevant Pages
|