[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: use directly makeinfo in texi2dvi instead of working around
From: |
Gavin Smith |
Subject: |
Re: use directly makeinfo in texi2dvi instead of working around |
Date: |
Sun, 13 Nov 2022 11:12:17 +0000 |
On Sat, Nov 12, 2022 at 12:47:21PM +0000, Gavin Smith wrote:
> On Wed, Aug 24, 2022 at 08:36:50PM +0200, Patrice Dumas wrote:
> > > My preference would be to leave the code as it is now, as it looks fairly
> > > complicated and it is one more thing to break when the code gets a
> > > wider audience after a new release, on top of other unexpected breakages,
> > > which we would struggle to process. There doesn't seem to be any
> > > pressing need to change this code.
> >
> > Ok, nothing urgent at all, it is just that I read about it in the manual
>
> The release is done so you could make this change if you wanted to,
> removing the lines from the bottom of README-hacking once you are
> done.
I've done it myself. I didn't change the makeinfo invocation. I don't
like the "-c TEXINFO_OUTPUT_FORMAT=plaintexinfo" option much but it is
not a big deal if you would rather use it. (My feeling is that
"plaintexinfo" is not very descriptive and that the TEXINFO_ prefix
is redundant.)
Another option would be to change texi2any not to process for output
with the invocation we use -
$makeinfo --footnote-style=end -I "$in_dir" $run_mi_includes \
-o /dev/null --macro-expand=-
- possibly if the --macro-expand option is given as this option is likely
only used in this script and for debugging.