On Tue, Oct 13, 2026 at 01:56:53PM +0200, Patrice Dumas wrote: > > I checked with a line like: > > > > Ref: ^HIndex cp^?894490 > > > > (i.e. with a special marker SPC BS) this shows up in the tab completion > > in standalone Info after the 'g' command as "^HIndex cp" at the start > > of the list. The leading space appears to be skipped when getting the > > anchor name - so probably using a leading space isn't a good idea for this. > > I do not get it.
I wasn't making an important point anyway. > > Another idea is to use some other control character, somewhat at random. > > "Ref: ^XIndex cp" for example. ^X doesn't appear to do anything when > > printed to a terminal, so this prints as "Ref: Index cp" if dumped to > > a terminal. In Info, after typing "g TAB", "^XIndex cp" is listed at > > the top of the completions pane, and you can select it by typing > > "^Q^XIndex cp RET". Emacs seems to work the same way. > > I think that we should try to use control characters we already use if > possible, therefore I would prefer ^H to ^X. I'm happy with using "^HIndex cp" as an anchor name for the "cp" index. > > So I think using a "^X" byte prefix would be ok. I'm also happy with > > the idea of not using a control character at all in the anchor name. > > I think that we should use a control character, and even make it a > (temporary, if 40 years can be considered temprary...) feature of the > Info format that something like > > Ref: ^HIndex^H toto^?894490 > > is to be considered to be exactly the same as > Index: toto^?894490 > > and is used as a workaround for standalone Info before 2025 not accepting > unknown tag table fields to add new tag table fields. The Info readers > would also handle the new tag table field, such that it would be forward > compatible. > > This would allow for a transition path: until 2045 have texi2any > output, for new tag table fields > Ref: ^HTiti^H ....^?894490 > after 2045 output > Titi: ....^?894490 > > And in Info readers handle both forms until 2065. We don't know what kind of computers people will be using in 2065 or whether people then will have any interest in the Info format so I suggest not thinking on such a long timeframe. You're also assuming that Texinfo is going to be actively maintained until then and follow a plan set out at the current date.
