> >>>>> "Scott" == Scott J Henson <[EMAIL PROTECTED]> writes:
> 
>   > It seems that in the last update to tetex(3) pdfetex was set as
>   > the default render engine for tex.  I am having problems with it
>   > in that it doesn't interpret environment variables in the tex
>   > files.  The old engine(etex) interpreted them properly.  Is there
>   > a way to switch back to etex or get pdfetex to interpret the
>   > environment variables?  Thank you.
> 
> It had never been intended that TeX supports environment variables.
> 
> I remember that there had been a discussion about it long time ago,
> but I don't remember any details.  Obviously somthing had been changed
> indeed a few years ago, but as I said before, it had never been
> intended to support environment variables.
> 
> You can still use environment variables in some situations, for
> instance
> 
> \catcode`\$=12
> \input $HOME/envtest.tex
> \bye
> 
> Does this work?  This is not a feature of TeX, it's the shell which
> expands $HOME.

it used to work here.  the first complaint i had was from a user,
after i had upgraded to tetex 3 -- dunno when the change occurred in
texlive terms.

i have a package that interprets env variables using \write18 (under
un*x).  it's a scrappy thing, re-hacked today, and not yet bedded-
down.  pretty trivial, for all that.

anyone fancies beta testing (it worked for me this afternoon, but...)
drop me a line.

Reply via email to