On Tue, Nov 29, 2022 at 01:30:22PM -0800, Per Bothner wrote:
> I believe best practice is for the first line of a commit message
> to be a self-contained short summary, followed by an empty line
> and further details (if any). So some editing of a ChangeLog entry
> is usually appropriate before usi
On Tue, Nov 29, 2022 at 05:29:47PM +0100, Vincent Lefevre wrote:
> Consider the following testcase:
>
> \input texinfo@c -*-texinfo-*-
> @afourpaper
> @page
> A
> @sp 31
> B
> @need 800
> C
> @sp 17
> D
> @bye
>
> to be compiled with texi2pdf. As of texinfo.tex 2022-08-21.14[*],
> the output
On 11/29/22 13:18, Gavin Smith wrote:
I have looked at the diff and found which parts of the code were
changed. Can you edit the following to describe the changes, and
send it back, or commit it yourself with a ChangeLog entry,
I'll do that.
One question that occured to be: Would it be cle
On Tue, Nov 29, 2022 at 10:45:24AM -0800, Per Bothner wrote:
> On 11/28/22 13:28, Gavin Smith wrote:
> > The indices go to the right place and they update the entries, but the
> > index text is wrong now: for example, in the Texinfo manual, type in
> > "author" and there is nothing, but type in "@t
On 11/28/22 13:28, Gavin Smith wrote:
The indices go to the right place and they update the entries, but the
index text is wrong now: for example, in the Texinfo manual, type in
"author" and there is nothing, but type in "@title" and
"@title @subtitle @author" is suggested, because there is an
in
Consider the following testcase:
\input texinfo@c -*-texinfo-*-
@afourpaper
@page
A
@sp 31
B
@need 800
C
@sp 17
D
@bye
to be compiled with texi2pdf. As of texinfo.tex 2022-08-21.14[*],
the output is incorrect: more than 3 inches remain after line B on
the first page, but line C appears on a n
