Hallöchen! Eli Zaretskii <[EMAIL PROTECTED]> writes:
> [...] > >> In my opinion this should be said in the documentation of the >> Texinfo file format. > > I'm not sure I understand what you wanted to say here. Currently, the mentioning of the Invocation node is a short subsection of the appendix "Tips and Hints" in Texinfo's documentation. Since it is really parsed by Info, it should be made an explicit requirement in the file format (ie in texinfo.texi), and not only in the GNU Coding Standard. > [...] > >> Additionially, as I already said in a follow-up to Stepan, it's >> not only about command-line options. I like the "description", >> "files", and "environment" sections in manpages as well. For >> example, where is the configuration file? In $HOME, /usr/etc, or >> somewhere below /var? A manpage tells you under "FILES". > > If this is important, we could have references to the relevant > sections after the options' description; some packages already do > that. (OTOH, many packages simply don't have anything to say on > these issues.) Right, the least invasive possibility is to write a new section in texinfo.texi explaining how to structure a node (and a couple of subnodes if appropriate) that comprise a manpage by and large. -- Torsten Bronger, aquisgrana, europa vetus ICQ 264-296-646 _______________________________________________ Texinfo home page: http://www.gnu.org/software/texinfo/ [email protected] http://lists.gnu.org/mailman/listinfo/bug-texinfo
