Re: use directly makeinfo in texi2dvi instead of working around

2022-11-13 Thread Patrice Dumas
On Sun, Nov 13, 2022 at 11:53:54AM +, Gavin Smith wrote: > On Sun, Nov 13, 2022 at 12:26:33PM +0100, Patrice Dumas wrote: > > On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote: > > > I've done it myself. I didn't change the makeinfo invocation. I don't > > > like the "-c TEXINFO_OUT

Re: use directly makeinfo in texi2dvi instead of working around

2022-11-13 Thread Gavin Smith
On Sun, Nov 13, 2022 at 12:26:33PM +0100, Patrice Dumas wrote: > On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote: > > 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

Re: use directly makeinfo in texi2dvi instead of working around

2022-11-13 Thread Patrice Dumas
On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote: > 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 v

Re: use directly makeinfo in texi2dvi instead of working around

2022-11-13 Thread Gavin Smith
On Sat, Nov 12, 2022 at 12:47:21PM +, 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

Re: use directly makeinfo in texi2dvi instead of working around

2022-11-12 Thread Gavin Smith
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 > > complicatedm 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, > > whic

Re: use directly makeinfo in texi2dvi instead of working around

2022-08-24 Thread Patrice Dumas
On Wed, Aug 24, 2022 at 05:36:09PM +0100, Gavin Smith wrote: > > This code is for the --macro-expand option which may not be used that > much although may be baked into build scripts and the like. texinfo.tex's > own macro expansion is nearly always good enough, as far as I'm aware. I think that

Re: use directly makeinfo in texi2dvi instead of working around

2022-08-24 Thread Gavin Smith
On Wed, Aug 24, 2022 at 05:38:08PM +0200, Patrice Dumas wrote: > Hello, > > The sed use in texi2dvi, with comment_iftex could be replaced > by a direct use of makeinfo, starting with 5.0, released in 16 February > 2013 (as stated in the comment). > > The following call would be the best, to avoid

use directly makeinfo in texi2dvi instead of working around

2022-08-24 Thread Patrice Dumas
Hello, The sed use in texi2dvi, with comment_iftex could be replaced by a direct use of makeinfo, starting with 5.0, released in 16 February 2013 (as stated in the comment). The following call would be the best, to avoid having a processing as Info done: makeinfo -c TEXINFO_OUTPUT_FORMAT=plainte