texinfo-doc-nonfree 4.13a-1 / usr / share / doc / texinfo / html / node.html

This file is indexed.

/usr/share/doc/texinfo/html/node.html is in texinfo-doc-nonfree 4.13a-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
<html lang="en">
<head>
<title>node - GNU Texinfo 4.13</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Texinfo 4.13">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Nodes.html#Nodes" title="Nodes">
<link rel="prev" href="Node-Menu-Illustration.html#Node-Menu-Illustration" title="Node Menu Illustration">
<link rel="next" href="makeinfo-Pointer-Creation.html#makeinfo-Pointer-Creation" title="makeinfo Pointer Creation">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This manual is for GNU Texinfo (version 4.13, 18 September 2008),
a documentation system that can produce both online information and a
printed manual from a single source.

Copyright (C) 1988, 1990, 1991, 1992, 1993, 1995, 1996, 1997,
1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008
Free Software Foundation, Inc.

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.2 or any later version published by the Free Software
     Foundation; with no Invariant Sections, with the Front-Cover Texts
     being ``A GNU Manual'', and with the Back-Cover Texts as in (a)
     below.  A copy of the license is included in the section entitled
     ``GNU Free Documentation License.''

     (a) The FSF's Back-Cover Text is: ``You are free to copy and modify
     this GNU Manual.  Buying copies from GNU Press supports the FSF in
     developing GNU and promoting software freedom.''
  -->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
  pre.display { font-family:inherit }
  pre.format  { font-family:inherit }
  pre.smalldisplay { font-family:inherit; font-size:smaller }
  pre.smallformat  { font-family:inherit; font-size:smaller }
  pre.smallexample { font-size:smaller }
  pre.smalllisp    { font-size:smaller }
  span.sc    { font-variant:small-caps }
  span.roman { font-family:serif; font-weight:normal; } 
  span.sansserif { font-family:sans-serif; font-weight:normal; } 
--></style>
</head>
<body>
<div class="node">
<a name="node"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="makeinfo-Pointer-Creation.html#makeinfo-Pointer-Creation">makeinfo Pointer Creation</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Node-Menu-Illustration.html#Node-Menu-Illustration">Node Menu Illustration</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Nodes.html#Nodes">Nodes</a>
<hr>
</div>

<h3 class="section">6.3 The <code>@node</code> Command</h3>

<p><a name="index-Node_002c-defined-300"></a><a name="index-node-301"></a>
A <dfn>node</dfn> is a segment of text that begins at an <code>@node</code>
command and continues until the next <code>@node</code> command.  The
definition of node is different from that for chapter or section.  A
chapter may contain sections and a section may contain subsections;
but a node cannot contain subnodes; the text of a node continues only
until the next <code>@node</code> command in the file.  A node usually
contains only one chapter structuring command, the one that follows
the <code>@node</code> line.  On the other hand, in printed output nodes
are used only for cross references, so a chapter or section may
contain any number of nodes.  Indeed, a chapter usually contains
several nodes, one for each section, subsection, and
subsubsection.

  <p>To specify a node, write an <code>@node</code> command at the beginning of
a line, and follow it with up to four arguments, separated by commas,
on the rest of the same line.  The first argument is required; it is
the name of this node (for details of node names, see <a href="Node-Line-Requirements.html#Node-Line-Requirements">Node Line Requirements</a>).  The subsequent arguments are the names of the `Next',
`Previous', and `Up' pointers, in that order, and may be omitted if
your Texinfo document is hierarchically organized (see <a href="makeinfo-Pointer-Creation.html#makeinfo-Pointer-Creation">makeinfo Pointer Creation</a>).

  <p><a name="index-accesskey_0040r_007b_002c-in-HTML-output_007d-302"></a>Whether the node pointers are specified implicitly or explicitly, the
HTML output from <samp><span class="command">makeinfo</span></samp> for each node includes links to
the `Next', `Previous', and `Up' nodes.  The HTML also uses the
<code>accesskey</code> attribute with the values &lsquo;<samp><span class="samp">n</span></samp>&rsquo;, &lsquo;<samp><span class="samp">p</span></samp>&rsquo;, and
&lsquo;<samp><span class="samp">u</span></samp>&rsquo; respectively.  This allows people using web browsers to
follow the nagivation using (typically) <kbd>M-</kbd><var>letter</var>, e.g.,
<kbd>M-n</kbd> for the `Next' node, from anywhere within the node.

  <p>You may insert spaces before each name on the <code>@node</code> line if
you wish; the spaces are ignored.  You must write the name of the node
and (if present) the names of the `Next', `Previous', and `Up'
pointers all on the same line.  Otherwise, the formatters fail. 
(see <a href="../info/index.html#Top">info</a>, for more information about nodes in Info.)

  <p>Usually, you write one of the chapter-structuring command lines
immediately after an <code>@node</code> line&mdash;for example, an
<code>@section</code> or <code>@subsection</code> line.  (See <a href="Structuring-Command-Types.html#Structuring-Command-Types">Structuring Command Types</a>.)

  <p>TeX uses <code>@node</code> lines to identify the names to use for cross
references.  For this reason, you must write <code>@node</code> lines in a
Texinfo file that you intend to format for printing, even if you do not
intend to format it for Info.  (Cross references, such as the one at the
end of this sentence, are made with <code>@xref</code> and related commands;
see <a href="Cross-References.html#Cross-References">Cross References</a>.)

<ul class="menu">
<li><a accesskey="1" href="Node-Names.html#Node-Names">Node Names</a>:                   How to choose node and pointer names. 
<li><a accesskey="2" href="Writing-a-Node.html#Writing-a-Node">Writing a Node</a>:               How to write an <code>@node</code> line. 
<li><a accesskey="3" href="Node-Line-Tips.html#Node-Line-Tips">Node Line Tips</a>:               Keep names short. 
<li><a accesskey="4" href="Node-Line-Requirements.html#Node-Line-Requirements">Node Line Requirements</a>:       Keep names unique, without @-commands. 
<li><a accesskey="5" href="First-Node.html#First-Node">First Node</a>:                   How to write a `Top' node. 
<li><a accesskey="6" href="makeinfo-top-command.html#makeinfo-top-command">makeinfo top command</a>:         How to use the <code>@top</code> command. 
</ul>

  </body></html>

APT Browse - Built by Thomas Orozco.