[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: texi2dvi changes
From: |
Gavin Smith |
Subject: |
Re: texi2dvi changes |
Date: |
Wed, 23 Sep 2015 00:39:34 +0100 |
On 22 September 2015 at 23:55, Karl Berry <address@hidden> wrote:
> 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.
Maybe something like
Index: ../texi2dvi
===================================================================
--- ../texi2dvi (revision 6637)
+++ ../texi2dvi (working copy)
@@ -709,6 +709,11 @@
generated_files_get ()
{
$generated_files_get_method "$in_noext"
+ if test $generated_files_get_method = generated_files_get_from_fls; then
+ if test -f "$in_noext.fl"; then
+ report 'WARNING!! You may typeset garbage!' # goes to stderr
+ fi
+ fi
}
More another time.
> Another approach, though suboptimal IMHO, would be for texinfo.tex and
> makeinfo to reject up front an attempt to "@defindex fl". That would be
> better than "successfully" typesetting junk. (I did my tests with the
> texinfo.tex currently in the repo, FWIW.)
It can be fixed in new texinfo.tex, but not in old texinfo.tex (that
would require time travel). So issuing a warning is better.