Re: emacs-29 889a550ca08: ; Fix Texinfo warnings

[Ihor Radchenko <yantar92@posteo.net>]

Eli Zaretskii <eliz@gnu.org> writes:

>> I do not see any clear reason why one may not put @anchor at the same
>> line with @item.
>
> I don't understand what you are saying here.  Are you saying that the
> warning is bogus and should not be emitted in this case?  Or that the
> Texinfo manual should explain better why @anchor should not appear on
> an @item line?  If so, please take this up with the Texinfo
> maintainers, and ask them either to change the code or to fix the
> manual.

I was hoping that you know and can quickly explain the reason.

> Me, I would simply move the @anchor line before the @item, where it
> belongs.  It will shut up the warning and also make the manual cleaner
> from the Texinfo POV.  (Thet's what I did in other cases where this
> warning was emitted by makeinfo 7.1.)  But that's me.

Moving _before_ @item is not an option. For example, consider

- This is a long list item, and we want to put an anchor <<<here>>>, in the middle of the line.

The anchor does not belong to item itself, it is linking to a specific
place in the text.

>> In Org mode, we add @anchor at the same place where the corresponding
>> Org markup (<<<radio target>>>) is placed.
>
> That's a mistake, IMO.  @anchor is basically the same as @node.

AFAIU, it is not. See the above example.

>> I guess we might try to put @anchor on a separate line just for the sake
>> of avoiding this warning, but I am not confident that it is always safe
>> and won't break Texinfo markup.
>
> It won't, since that's how @anchor is supposed to be used.

Does it mean that something like

@item This is
@anchor{my-anchor}
a single paragraph inside item.

is always safe?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>