[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: texi2dvi changes
From: |
Gavin Smith |
Subject: |
Re: texi2dvi changes |
Date: |
Tue, 22 Sep 2015 23:59:37 +0100 |
On 22 September 2015 at 23:55, Karl Berry <address@hidden> wrote:
> Hi Gavin,
>
> gs> If someone uses an "fl" index with the recorder, I expect either
> the index to be blank, or to be the recorder file interpreted as TeX
> source (a great ugly mess).
>
> There's a comment in texi2dvi that says
> # The default behaviour is `nomaybe'.
> But the actual default for TEXI2DVI_USE_RECORDER is yesmaybe (line 1530).
>
> Excuse my opinion, but this seems like the worst possible outcome. This
> way, an existing document that uses an fl index (as discussed, they
> exist) will silently typeset garbage with a new texi2dvi. Thus, with
> the yesmaybe default, I strongly believe that texi2dvi should give a
> definite error in the case of both the recorder being used and the fl
> index being used.
I changed this to nomaybe in my last commit (and also noticed the
comment was wrong).
> On another front: evidently some grep for openout is not being redirected.
> (Looks like that's the case in check_openout_in_log_support.)
> With attached, stdout from texi2dvi indexfl.texi starts with
> \openout0 = `dum.dum'.
Also fixed in last commit.