Answers inserted below...
Le 16/09/2015 11:09, Gavin Smith a écrit :
>> Since the nearly beginning of this whole tale of woe, I am thinking that
>> it would be better to solve the .fls case in texinfo.tex also rather
>> than just texi2dvi, my first idea was some fl<->_0 translation, and my
>>
On 18 September 2015 at 08:09, Vincent Belaïche
wrote:
> Answers inserted below...
>
> Le 16/09/2015 11:09, Gavin Smith a écrit :
>> I don't think we should change the file extensions any more than in
>> necessary (.fl and .fls possibly).
>
> That was my previous idea
On 17 September 2015 at 20:20, Eli Zaretskii wrote:
> In the beginning there was only 'test -n "$COMSPEC$ComSpec"', and the
> comment still says so. Then someone wanted to exclude Cygwin from
> that (since Cygwin is a Posix emulation, so it uses ':' even though
> $ComSpec is set,
On 18 September 2015 at 08:09, Vincent Belaïche
wrote:
> It could not be so big, because we should make texi2dvi/texindex
> backward compatible with the older extensions and make the update in
> texinfo.tex one or two years later than for texi2dvi/texindx, assuming
>
I would guess that bonus is there to try to get an @example not to
span more than one page.
Right.
On the other hand, it's true enough that the text before an example
usually leads into the example. It seems like this is true of any
environment. Thus perhaps the \penalty-50 should
I was experimenting with adding a page break penalty at the start of
an @example, and some other display environments, because in material
like:
If you want to remove a preinstalled AUC@TeX{} completely before any of
its modes have been used,
@example
(unload-feature 'tex-site)
@end example
On 18 September 2015 at 14:30, Gavin Smith wrote:
> After mulling it over, I've come up with the following:
>
> Index: texi2dvi
> ===
> --- texi2dvi(revision 6632)
> +++ texi2dvi(working copy)
> @@
On 18 September 2015 at 09:52, Gavin Smith wrote:
>> I agree, but on the other hand I must now withdraw what I had previously
>> written: the current fix in fact does not work as expected for MikTeX. I
>> had thought that everything was fine because the compilation went
On 18 September 2015 at 14:43, Gavin Smith wrote:
> So this doesn't work. I reordered TEXINPUTS to put the working
> directory first, and the index displays as non-existent. I put in a
> breakpoint in texinfo.tex in \printindex (with \show), and had a look
> at the files