> Cc: [email protected] > From: Per Bothner <[email protected]> > Date: Tue, 31 Oct 2017 14:18:29 -0700 > > > IMO, if we are going to have such a feature, it should be a new > > command, like @defunidx or somesuch. > > How about @dref ?
I'm not good with names, but @dref sounds like a command from the *ref family (@xref, @pxref, etc.), which it isn't. > > and the usual way to find them > > quickly is to type "i FUNCTION" in the Info reader, which is almost as > > fast as following an explicit cross-reference. > > Fast but unreliable. In HTML the marking (usually underline) for > a link makes it clear that it *is* a link, and selecting it will > take you to the correct place, rather than just one with the same name. I don't see what does this have to do with reliability. Index-search is a very basic and important feature of Info. If you are arguing for having each indexed phrase that is also literally in the text (something that frequently doesn't happen), then I think I'm in favor. But that's a separate discussion, I think. > > Using a colon is not a good idea, IMO: the Texinfo manual explicitly > > warns against using it in node names, for similar reasons. > > I don't see a warning about colons in the 'Choosing Node Names'. That's because you didn't use 'i' ;-) This is described in "Node Line Requirements".
