Re: Relating multiple index entries to one table item
Eli Zaretskii <[email protected]>
| Newsgroups | gmane.comp.tex.texinfo.general |
|---|---|
| Message-ID | <[email protected]> |
> From: Arsen Arsenović <[email protected]> > Date: Sun, 20 Nov 2022 19:44:30 +0100 > > In the GCC documentation, a construct that often appears is > > @table @gcctabopt > @item -Wpedantic > @itemx -pedantic > @opindex pedantic > @opindex Wpedantic > @opindex Wno-pedantic > > The problem with this, though, is that all but the first of these index > calls end up in the item body rather than the item itself, meaning that > all but the first index will scroll HTML pages below the actual items. > This result is not very pleasant to see, since it strips away essential > context from the reader. I tried working around this by interlacing > @opindex calls between /@itemx?/ calls, but that didn't really help. The index entries should precede the first @item, not be after it. Maybe doing so doesn't work in this case, but you should move the index entries before the @item/@itemx lines regardless, since otherwise the indexing commands will not land you where you want.