On Mon, Mar 20, 2023 at 06:27:00PM +0000, Werner LEMBERG wrote:
> > This was a deliberate change to make index commands terminate
> > paragraphs.
>
> Well, it stayed completely undocumented...
It is in NEWS, but not in a released version admittedly.
> > This was intended for input like the following: [...] so that the
> > @?index command could precede the @item line they referred to
> > without being part of the preceding paragraph, and without the need
> > for an extra blank line in the Texinfo source or Info output.
> >
> > Does this change cause a problem?
>
> Yes, it does. In LilyPond's Notation Reference, we have a lot of code
> like the following.
>
> ```
> @subheading Predefined commands
>
> @raggedright
> @findex \virgula
> @code{\virgula},
> @findex \caesura
> @code{\caesura},
> @findex \divisioMinima
> @code{\divisioMinima},
> @findex \divisioMaior
> @code{\divisioMaior},
> @findex \divisioMaxima
> @code{\divisioMaxima},
> @findex \finalis
> @code{\finalis}.
> @end raggedright
> ```
I looked at where this was used in the manual in question and it wasn't
obvious that the index entries were in the right place as all the
"Predefined commands" section was was a list of commands but no explanation
of those commands. It was close enough to the explanation that the
location of the index entries may have been okay, though.
I can't think of a way right now of supporting this with the current
approach. One possibility is to revert the change and try to think
of another way of solving the original problem, maybe one restricted
to @table and similar commands. The texinfo.texi manual was changed
on 2022-11-26 to make this change ("Move index commands before @item
in @table") and could be changed back again if we got a better solution.
IIRC the main problem is in HTML output with vertical scrolling of
links from HTML index entries being too far down the page leading the
heading to not be visible.
