jfbu <j...@free.fr> writes: > Le 30/04/2015 10:09, jfbu a écrit : >> Thu Apr 30 10:04:30 CEST 2015 + kpsewhich --progname latex > --expand-path $SYSTEXMF > > besides, shouldn't all those be > > kpsewhich --var-value SYSTEXMF > > etc ... ? > > indeed for example on my system I don't have any environment variable > set relative to the TeX installation ... > > All the relevant path are all set-up in the texmf.cnf file > from the TeXLive distribution. > > from http://tug.org/texinfohtml/kpathsea.html#Path-expansion > > 5.3.2 Variable expansion > > ‘$foo’ or ‘${foo}’ in a path element is replaced by (1) the value of > an environment variable ‘foo’ (if defined); (2) the value of ‘foo’ > from texmf.cnf (if defined); (3) the empty string. > > But with the syntax > > kpsewhich --progname latex --expand-path $SYSTEXMF > > $SYSTEXMF is not there as a path element
If it weren't, your logging program would have had a hard time showing its name, wouldn't it? -- David Kastrup _______________________________________________ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex