Re: [AUCTeX] Long loading time

[jfbu]

Le 30/04/2015 10:35, David Kastrup a écrit :
> jfbu <address@hidden> 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?

the logging wrapper logged the arguments. When I tried manually
from a Terminal, the shell expanded $SYSTEXMF and it expanded to nil
because I don't have any such environment variable.

Does AUCTeX set up a shell with suitable SYSTEXMF environment variables?

in that case what is the point of the call to kpsewhich?

wrapper:

#!/bin/bash
#
#
OPTIONS="$@"
#
echo "`date` + kpsewhich "$@"" >> /Users/---/Downloads/KPSELOG
#
exec /usr/texbin/kpsewhich "$@"

Jean-François