[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
@node
Line RequirementsHere are several requirements for @node
lines:
Duplicates confuse the Info movement commands. This means, for example, that if you end every chapter with a summary, you must name each summary node differently. You cannot just call each one “Summary”. You may, however, duplicate the titles of chapters, sections, and the like. Thus you can end each chapter in a book with a section called “Summary”, so long as the node names for those sections are all different.
The node to which a pointer points may come before or after the node containing the pointer.
@
and {
. For a few
rare cases when this is useful, Texinfo has limited support for using
@-commands in node names; see Pointer Validation.
Thus, the beginning of the section called @chapter
looks like
this:
@node chapter, unnumbered & appendix, makeinfo top, Structuring @comment node-name, next, previous, up @section @code{@@chapter} @findex chapter
For example, the following is a section title:
@code{@@unnumberedsec}, @code{@@appendixsec}, @code{@@heading}
The corresponding node name is:
unnumberedsec appendixsec heading
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on a sunny day using texi2html.