Re: @anchor on @item line

[Gavin Smith <gavinsmith0123@gmail.com>]

On Sun, Nov 12, 2023 at 07:23:41PM +0000, Gavin Smith wrote:
> There is actually a problem with @ftable and @vtable.  If you put an
> @anchor on an @item line there, then it is the text of an index entry,
> which is a real problem.

Further to this, if @anchor should be allowed inside @item as long as the
@item is not creaing an index entry, it should also be allowed inside
@defline and @deftypeline (these are new commands), as these do not create
index entries.

I have made a commit today to allow @anchor in @item and also these
other commands, and will also add this change to the release branch so
that if there is ever a 7.1.1 release, this fix will be included.

We may still not want to allow other "non-basic inline" commands
(e.g. @xref) inside @item/@defline/@deftypeline as inappropriate for
one reason or another, but at the moment it seems the easiest way forward
is to allow these.

@anchor used inside @item inside @ftable/@vtable still leads to a warning
if the index is output, just the warning is slightly obscure.

I thought of allowing @anchor as basic inline content, but we would have
to come up with some other mechanism for detecting and warning about
@anchor inside index entries, and there are too many other commands where
we truly should not have @anchors (e.g. @node names, as cross-references
to those nodes would have to have the @anchor in them).  @anchor should
not appear in any context where it does not correspond to a single
position in the output file.