>> Why can't the third argument be automatically generated as well?
>> It seems inconsistent to use the anchor name in cross-references
>> while not using node names in cross-references.
>
> The problem is that LilyPond's xref generator doesn't know whether
> the target is a `@node` or an `@anchor`. [...]
After some thinking I agree that this is the way to go for LilyPond's
Internal Reference. However, ...
> Anyway, I think it makes sense to change the one-argument `@xref`
> and friends to produce a better default.
... this is still my opinion.
Werner
