Re: texinfo: warning: @anchor should not appear on @item line

Georg-Johann Lay <[email protected]> Mon, 18 Mar 2024 20:41:08 +0100
Newsgroups gmane.comp.tex.texinfo.general
Message-ID <[email protected]>

Am 18.03.24 um 19:41 schrieb Patrice Dumas:
> On Mon, Mar 18, 2024 at 07:30:40PM +0100, Georg-Johann Lay wrote:
>>
>>
>>> In my tests it seems so.  If a @vtable is used instead of a @table and
>>> a printindex is used too, there are two <a> generated for the anchor,
>>> but it does not seems to me to problematic.  More problematic is that
>>> there is no visible link to the index entry generated in the @printindex
>>> formatting, which could be investigated.
>>
>> Hi Patrice,
>>
>> thanks for the swift answer.  In my specific case it is only about
>> @table @code.  If I understand you correctly, then this was a glitch
>> in texinfo, and not that @anchor and @item are fundamentally
>> incompatible.  That's good to hear.
> 
> Well, I would say that it is borderline.  I do not like that it
> is ok in @table and not in @vtable for instance, the constructs correct
> in both should be the same.
> 
> Even if it not exactly the same and probably does not gives you the
> exact expected output, I think that the following would be a more
> expected construct:
> 
> @table @code
> 
> @item label1
> @anchor{label1}
> Text1
> 
> @end table

But this gives an ugly result.  When clicking on "labelX" (and there is
much text prior to it) then the browser screen will look like

label1
<top-of-screen>
   Text1

i.e. label1 is not visible. What I want is


<top-of-screen>
label1
   Text1

Johann