> From: David Malcolm <[email protected]> > Cc: [email protected] > Date: Fri, 15 Feb 2019 14:03:26 -0500 > > > Why not use @anchor and @xref? Those should produce visible links. > > I'm hoping for some kind of way to get the toolchain to automatically > generate the HTML I want without having to touch all of the options in > our .texi source to get this. FWIW, these items are within a "@table > @gcctabopt", and, now I look at it, gcctabopt is a GCC-specific texinfo > macro [1]. > > So maybe it's possible to fix this at our end by making that macro > smarter, somehow? (I'm definitely not an expert here). Presumably I > want the macro I want to extract any opindex within the item, and > repeat it, within an @anchor. Is this kind of thing expressible via > texinfo macros? > > Unfortunately, I run into things like: > > ../../src/gcc/doc/cpp.texi:4375: warning: @anchor should not appear in @table > (possibly involving @gcctabopt) > ../../src/gcc/doc/cpp.texi:4375: empty argument in @anchor (possibly > involving @gcctabopt) > ../../src/gcc/doc/cpp.texi:4375: table requires an argument: the formatter > for @item > > when experimenting with e.g.: > > @macro gcctabopt{body} > @anchor{\body\} > @end macro > > as an alternative implementation of that macro.
You just need to come up with a smarter macro, or maybe 2 separate macros. Sorry, cannot say more, since the URL you posted points only to the definition of the macro, not its usage.
