This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: [Standards References] @def vs. @item
- From: Rical Jasan <ricaljasan at pacific dot net>
- To: "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Thu, 20 Oct 2016 23:45:38 -0700
- Subject: Re: [Standards References] @def vs. @item
- Authentication-results: sourceware.org; auth=none
- References: <7c6c7080-822f-b2de-fcca-3998b5fefb21@pacific.net>
After some experimentation, and brushing up on my Texinfo, I was able to
make some aliases and macros work in various combinations, but I
stumbled across this little nugget in [1]:
"The @table command works with other commands besides those explicitly
mentioned here. However, you can only use predefined Texinfo commands
that take an argument in braces. You cannot reliably use a new command
defined with @macro, although an @alias (for a suitable predefined
command) is acceptable."
My context must be off, or something, because I could make macros for
@item work in the table, but not aliases. Given the weight of that
caveat, however ("cannot reliably"), probably better to just make the
syntax-checker smarter in the meantime, while we figure out what we're
really going to do with the header and standards @comments.
This boils down to struct members being given as @items in a @table
within the @deftp for the struct, btw, which really is quite a nice way
to do it, so I'd rather leave it as-is if the @defsm option [2] isn't
viable.
Rical
[1]
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040table.html
[2] @c wrapper for struct member @items
@macro defsm{item}
@item \item\
@end macro
p.s. $ texi2pdf --version
texi2pdf (GNU Texinfo 6.1) 6991