From: Fabrice Popineau <[EMAIL PROTECTED]>
Subject: \jobname
>
>
> Before I spend time on it, does anybody knows why :
>
> D:\tmp>tex "&latex" "\input foo.tex"
>
> produces foo.dvi
>
> and
>
> D:\tmp>tex "&latex" "\renewcommand\encodingdefault{T1}\selectfont\input foo.tex"
>
> produces t
From: Fabrice Popineau <[EMAIL PROTECTED]>
Subject: \jobname
>
>
> Before I spend time on it, does anybody knows why :
>
> D:\tmp>tex "&latex" "\input foo.tex"
>
> produces foo.dvi
>
> and
>
> D:\tmp>tex "&latex" "\renewcommand\encodingdefault{T1}\selectfont\input foo.tex"
>
> produces t
Before I spend time on it, does anybody knows why :
D:\tmp>tex "&latex" "\input foo.tex"
produces foo.dvi
and
D:\tmp>tex "&latex" "\renewcommand\encodingdefault{T1}\selectfont\input foo.tex"
produces texput.dvi? Shouldn't jobname be set accordingly to the
first filename \input?
--
Fabrice
Olaf Weber <[EMAIL PROTECTED]> writes:
> That's odd: the C standard took a lot of care to ensure that implicit
> declarations would, in fact, continue to work. So this sounds like
> there is a possible conformance issue with the compiler and/or
> standard library lurking here.
Not quite.
The
Adrian Bunk writes:
> Bdale Garbee <[EMAIL PROTECTED]> reported the following problem with
> the 20001218 beta of teTeX:
> <-- snip ->
> The configure script in the texk/kpathsea directory seg faults when
> running the test program that checks whether putenv uses malloc.
> The problem is tha
Hi,
Bdale Garbee <[EMAIL PROTECTED]> reported the following problem with
the 20001218 beta of teTeX:
<-- snip ->
The configure script in the texk/kpathsea directory seg faults when running
the test program that checks whether putenv uses malloc. The problem is that
the test program doesn't
