> Your proposal from a few days ago of using a @*heading command
> appears relevant. We could use a command like
> "@xrefanchorlabelisheading" (hard to get a descriptive, short name).
>
> So with input like:
>
> @heading Bögen
> @anchor{Bows}
>
> Then @ref{Bows} would produce "Bögen", etc.
>
> If that is not enough, [...]
This is exactly what I'm after, and it would be fully sufficient,
thanks.
> The only downside is that we would be adding a new command for what
> seems like a fairly niche use case.
Maybe it's a niche use case, but as I've just written in another mail,
having a pendant to `@node` & `@xref` for sectioning commands that
don't have an associated `@node` would make Texinfo more symmetrical.
>> * With my suggestion, if a `@node` gets converted to `@anchor` for
>> whatever reason, all references from external files appear
>> exactly the same if `@xrefautomaticsectiontitle` is active – and
>> LilyPond has *a lot* of external references... Without it, the
>> reference suddenly shows something else, and it would be
>> necessary to modify the reference command by adding the old
>> sectioning name as a third argument to get that back.
>
> I'm confused what you mean by "external files". [...]
Sorry, I mixed this up. This is for for the same Texinfo manual, of
course.
Werner