[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
texinfo ChangeLog doc/texinfo.txi
|
From: |
Karl Berry |
|
Subject: |
texinfo ChangeLog doc/texinfo.txi |
|
Date: |
Fri, 15 Jun 2012 18:31:38 +0000 |
CVSROOT: /sources/texinfo
Module name: texinfo
Changes by: Karl Berry <karl> 12/06/15 18:31:38
Modified files:
. : ChangeLog
doc : texinfo.txi
Log message:
remove unneeded @refill
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/texinfo/ChangeLog?cvsroot=texinfo&r1=1.1373&r2=1.1374
http://cvs.savannah.gnu.org/viewcvs/texinfo/doc/texinfo.txi?cvsroot=texinfo&r1=1.445&r2=1.446
Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/texinfo/texinfo/ChangeLog,v
retrieving revision 1.1373
retrieving revision 1.1374
diff -u -b -r1.1373 -r1.1374
--- ChangeLog 14 Jun 2012 18:13:51 -0000 1.1373
+++ ChangeLog 15 Jun 2012 18:31:38 -0000 1.1374
@@ -1,3 +1,7 @@
+2012-06-15 Karl Berry <address@hidden>
+
+ * doc/texinfo.txi: remove all now-unnecessary @refill's.
+
2012-06-14 Patrice Dumas <address@hidden>
and Karl Berry <address@hidden>
Index: doc/texinfo.txi
===================================================================
RCS file: /sources/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.445
retrieving revision 1.446
diff -u -b -r1.445 -r1.446
--- doc/texinfo.txi 14 Jun 2012 18:13:51 -0000 1.445
+++ doc/texinfo.txi 15 Jun 2012 18:31:38 -0000 1.446
@@ -1,5 +1,5 @@
\input texinfo.tex @c -*-texinfo-*-
address@hidden $Id: texinfo.txi,v 1.445 2012/06/14 18:13:51 karl Exp $
address@hidden $Id: texinfo.txi,v 1.446 2012/06/15 18:31:38 karl Exp $
@c Ordinarily, Texinfo files have the extension .texi. But texinfo.texi
@c clashes with texinfo.tex on 8.3 filesystems, so we use texinfo.txi.
@@ -1096,19 +1096,19 @@
point to any other nodes, and a menu can contain any other nodes.
Thus, the node structure can be any directed graph. But it is usually
more comprehensible to follow a structure that corresponds to the
-structure of chapters and sections in a printed book or address@hidden
+structure of chapters and sections in a printed book or report.
In addition to menus and to `Next', `Previous', and `Up' pointers, Info
provides pointers of another kind, called references, that can be
sprinkled throughout the text. This is usually the best way to
-represent links that do not fit a hierarchical address@hidden
+represent links that do not fit a hierarchical structure.
Usually, you will design a document so that its nodes match the
structure of chapters and sections in the printed output. But
occasionally there are times when this is not right for the material
being discussed. Therefore, Texinfo uses separate commands to specify
the node structure for the Info file and the section structure for the
-printed address@hidden
+printed output.
Generally, you enter an Info file through a node that by convention is
named `Top'. This node normally contains just a brief summary of the
@@ -1133,7 +1133,7 @@
@c /usr/local/lib/info
The @file{dir} file in the @file{info} directory serves as the
departure point for the whole Info system. From it, you can reach the
-`Top' nodes of each of the documents in a complete Info address@hidden
+`Top' nodes of each of the documents in a complete Info system.
@cindex URI syntax for Info
If you wish to refer to an Info file in a URI, you can use the
@@ -1170,13 +1170,13 @@
A Texinfo-based book is similar to any other typeset, printed work: it
can have a title page, copyright page, table of contents, and preface,
as well as chapters, numbered or unnumbered sections and subsections,
-page headers, cross references, footnotes, and address@hidden
+page headers, cross references, footnotes, and indices.
You can use Texinfo to write a book without ever having the intention
of converting it into online information. You can use Texinfo for
writing a printed novel, and even to write a printed memo, although
this latter application is not recommended since electronic mail is so
-much address@hidden
+much easier.
@TeX{} is a general purpose typesetting program. Texinfo provides a
file @file{texinfo.tex} that contains information (definitions or
@@ -1207,7 +1207,7 @@
called WEB and can be compiled either in Pascal or (by using a
conversion program that comes with the @TeX{} distribution) in C.
(@xref{TeX Mode, ,@TeX{} Mode, emacs, The GNU Emacs Manual}, for information
-about @TeX{}.)@refill
+about @TeX{}.)
@TeX{} is very powerful and has a great many features. Because a
Texinfo file must be able to present information both on a
@@ -1227,7 +1227,7 @@
@code{texinfo-format-buffer} how to create an Info file are preceded
by @samp{@@}; they are called @dfn{@@-commands}. For example,
@code{@@node} is the command to indicate a node and @code{@@chapter}
-is the command to indicate the start of a address@hidden
+is the command to indicate the start of a chapter.
@quotation Note
Almost all @@ command names are entirely lower case.
@@ -1238,7 +1238,7 @@
by @TeX{} and by the code that converts them into Info files. You can
display Info files on any terminal that displays alphabetic and
numeric characters. Similarly, you can print the output generated by
address@hidden on a wide variety of address@hidden
address@hidden on a wide variety of printers.
Depending on what they do or what address@hidden word
@dfn{argument} comes from the way it is used in mathematics and does not
@@ -1262,17 +1262,17 @@
@item
Write a command such as @code{@@chapter} at the beginning of a line
followed by the command's arguments, in this case the chapter title, on
-the rest of the line. (@code{@@chapter} creates chapter titles.)@refill
+the rest of the line. (@code{@@chapter} creates chapter titles.)
@item
Write a command such as @code{@@address@hidden@}} wherever you wish but usually
-within a sentence. (@code{@@address@hidden@}} creates an ellipsis
@dots{})@refill
+within a sentence. (@code{@@address@hidden@}} creates an ellipsis @dots{})
@item
Write a command such as @code{@@address@hidden@address@hidden wherever you
wish (but usually within a sentence) with its argument,
@var{sample-code} in this example, between the braces. (@code{@@code}
-marks text as being code.)@refill
+marks text as being code.)
@item
Write a command such as @code{@@example} on a line of its own; write the
@@ -1290,7 +1290,7 @@
As a general rule, a command requires braces if it mingles among other
text; but it does not need braces if it starts a line of its own. The
non-alphabetic commands, such as @code{@@:}, are exceptions to the rule;
-they do not need address@hidden
+they do not need braces.
As you gain experience with Texinfo, you will rapidly learn how to
write the different commands: the different ways to write commands
@@ -1893,33 +1893,33 @@
@itemize @bullet
@item
-Insert frequently used @@-commands. @refill
+Insert frequently used @@-commands.
@item
Automatically create @code{@@node} lines.
@item
-Show the structure of a Texinfo source address@hidden
+Show the structure of a Texinfo source file.
@item
Automatically create or update the `Next',
`Previous', and `Up' pointers of a node.
@item
-Automatically create or update address@hidden
+Automatically create or update menus.
@item
-Automatically create a master address@hidden
+Automatically create a master menu.
@item
-Format a part or all of a file for address@hidden
+Format a part or all of a file for Info.
@item
-Typeset and print part or all of a address@hidden
+Typeset and print part or all of a file.
@end itemize
Perhaps the two most helpful features are those for inserting frequently
-used @@-commands and for creating node pointers and address@hidden
+used @@-commands and for creating node pointers and menus.
@node Emacs Editing
@section The Usual GNU Emacs Editing Commands
@@ -1932,7 +1932,7 @@
commands that should be on lines of their own are not inadvertently
included in paragraphs. Thus, the @kbd{M-q} (@code{fill-paragraph})
command will refill a paragraph but not mix an indexing command on a
-line adjacent to it into the address@hidden
+line adjacent to it into the paragraph.
In addition, Texinfo mode sets the @code{page-delimiter} variable to
the value of @code{texinfo-chapter-level-regexp}; by default, this is
@@ -1942,7 +1942,7 @@
@kbd{C-x ]} (@code{forward-page}) and @kbd{C-x [}
(@code{backward-page}) commands and narrow to a chapter with the
@kbd{C-x n p} (@code{narrow-to-page}) command. (@xref{Pages, , ,emacs,
-The GNU Emacs Manual}, for details about the page commands.)@refill
+The GNU Emacs Manual}, for details about the page commands.)
You may name a Texinfo file however you wish, but the convention is to
end a Texinfo file name with one of the extensions
@@ -1955,12 +1955,12 @@
when you visit a
file that has @samp{-*-texinfo-*-} in its first line. If ever you are
in another mode and wish to switch to Texinfo mode, type @code{M-x
address@hidden
+texinfo-mode}.
Like all other Emacs features, you can customize or enhance Texinfo
mode as you wish. In particular, the keybindings are very easy to
change. The keybindings described here are the default or standard
address@hidden
+ones.
@node Inserting
@section Inserting Frequently Used Commands
@@ -1970,23 +1970,23 @@
Texinfo mode provides commands to insert various frequently used
@@-commands into the buffer. You can use these commands to save
address@hidden
+keystrokes.
The insert commands are invoked by typing @kbd{C-c} twice and then the
-first letter of the @@-command:@refill
+first letter of the @@-command:
@table @kbd
@item C-c C-c c
@itemx M-x texinfo-insert-@@code
@findex texinfo-insert-@@code
Insert @code{@@address@hidden@}} and put the
-cursor between the address@hidden
+cursor between the braces.
@item C-c C-c d
@itemx M-x texinfo-insert-@@dfn
@findex texinfo-insert-@@dfn
Insert @code{@@address@hidden@}} and put the
-cursor between the address@hidden
+cursor between the braces.
@item C-c C-c e
@itemx M-x texinfo-insert-@@end
@@ -1994,19 +1994,19 @@
Insert @code{@@end} and attempt to insert the correct following word,
such as @samp{example} or @samp{table}. (This command does not handle
nested lists correctly, but inserts the word appropriate to the
-immediately preceding list.)@refill
+immediately preceding list.)
@item C-c C-c i
@itemx M-x texinfo-insert-@@item
@findex texinfo-insert-@@item
Insert @code{@@item} and put the
-cursor at the beginning of the next address@hidden
+cursor at the beginning of the next line.
@item C-c C-c k
@itemx M-x texinfo-insert-@@kbd
@findex texinfo-insert-@@kbd
Insert @code{@@address@hidden@}} and put the
-cursor between the address@hidden
+cursor between the braces.
@item C-c C-c n
@itemx M-x texinfo-insert-@@node
@@ -2014,44 +2014,44 @@
Insert @code{@@node} and a comment line
listing the sequence for the `Next',
`Previous', and `Up' nodes.
-Leave point after the @code{@@address@hidden
+Leave point after the @code{@@node}.
@item C-c C-c o
@itemx M-x texinfo-insert-@@noindent
@findex texinfo-insert-@@noindent
Insert @code{@@noindent} and put the
-cursor at the beginning of the next address@hidden
+cursor at the beginning of the next line.
@item C-c C-c s
@itemx M-x texinfo-insert-@@samp
@findex texinfo-insert-@@samp
Insert @code{@@address@hidden@}} and put the
-cursor between the address@hidden
+cursor between the braces.
@item C-c C-c t
@itemx M-x texinfo-insert-@@table
@findex texinfo-insert-@@table
Insert @code{@@table} followed by a @key{SPC}
-and leave the cursor after the @address@hidden
+and leave the cursor after the @key{SPC}.
@item C-c C-c v
@itemx M-x texinfo-insert-@@var
@findex texinfo-insert-@@var
Insert @code{@@address@hidden@}} and put the
-cursor between the address@hidden
+cursor between the braces.
@item C-c C-c x
@itemx M-x texinfo-insert-@@example
@findex texinfo-insert-@@example
Insert @code{@@example} and put the
-cursor at the beginning of the next address@hidden
+cursor at the beginning of the next line.
@c address@hidden was the binding for texinfo-insert-braces;
@c in Emacs 19, backward-paragraph will take this binding.
@item C-c C-c @{
@itemx M-x texinfo-insert-braces
@findex texinfo-insert-braces
-Insert @address@hidden@}} and put the cursor between the address@hidden
+Insert @address@hidden@}} and put the cursor between the braces.
@item C-c @}
@itemx C-c ]
@@ -2060,7 +2060,7 @@
Move from between a pair of braces forward past the closing brace.
Typing @kbd{C-c ]} is easier than typing @kbd{C-c @}}, which
is, however, more mnemonic; hence the two keybindings. (Also, you can
-move out from between braces by typing @kbd{C-f}.)@refill
+move out from between braces by typing @kbd{C-f}.)
@end table
To put a command such as @address@hidden@@address@hidden@address@hidden around
an
@@ -2072,13 +2072,13 @@
word or words. If you do not specify a prefix argument, Emacs inserts
the @@-command string and positions the cursor between the braces. This
feature works only for those @@-commands that operate on a word or words
-within one line, such as @code{@@kbd} and @code{@@address@hidden
+within one line, such as @code{@@kbd} and @code{@@var}.
This set of insert commands was created after analyzing the frequency
with which different @@-commands are used in the @cite{GNU Emacs
Manual} and the @cite{GDB Manual}. If you wish to add your own insert
commands, you can bind a keyboard macro to a key, use abbreviations,
-or extend the code in @address@hidden
+or extend the code in @file{texinfo.el}.
@findex texinfo-start-menu-description
@cindex Menu description, start
@@ -2089,19 +2089,19 @@
description in a menu entry line. (A menu entry has three parts, the
entry name, the node name, and the description. Only the node name is
required, but a description helps explain what the node is about.
address@hidden Parts, , The Parts of a Menu}.)@refill
address@hidden Parts, , The Parts of a Menu}.)
To use @code{texinfo-start-menu-description}, position point in a menu
entry line and type @kbd{C-c C-c C-d}. The command looks for and copies
the title that goes with the node name, and inserts the title as a
description; it positions point at beginning of the inserted text so you
can edit it. The function does not insert the title if the menu entry
-line already contains a address@hidden
+line already contains a description.
This command is only an aid to writing descriptions; it does not do the
whole job. You must edit the inserted text since a title tends to use
the same words as a node name but a useful description uses different
address@hidden
+words.
@node Showing the Structure
@section Showing the Section Structure of a File
@@ -2122,20 +2122,20 @@
called the @samp{*Occur*} buffer. In that buffer, you can position
the cursor over one of the lines and use the @kbd{C-c C-c} command
(@code{occur-mode-goto-occurrence}), to jump to the corresponding spot
-in the Texinfo address@hidden
+in the Texinfo file.
@table @kbd
@item C-c C-s
@itemx M-x texinfo-show-structure
@findex texinfo-show-structure
Show the @code{@@chapter}, @code{@@section}, and such lines of a
-Texinfo address@hidden
+Texinfo file.
@item C-c C-c
@itemx M-x occur-mode-goto-occurrence
@findex occur-mode-goto-occurrence
Go to the line in the Texinfo file corresponding to the line under the
-cursor in the @file{*Occur*} address@hidden
+cursor in the @file{*Occur*} buffer.
@end table
If you call @code{texinfo-show-structure} with a prefix argument by
@@ -2152,7 +2152,7 @@
@code{texinfo-show-structure} will work on only that region. To see
the whole buffer again, use @address@hidden n w}} (@code{widen}).
(@xref{Narrowing, , , emacs, The GNU Emacs Manual}, for more
-information about the narrowing commands.)@refill
+information about the narrowing commands.)
@vindex page-delimiter
@cindex Page delimiter in Texinfo mode
@@ -2163,7 +2163,7 @@
commands to move forward and backward by chapter, and to use the
@kbd{C-x n p} (@code{narrow-to-page}) command to narrow to a chapter.
@xref{Pages, , , emacs, The GNU Emacs Manual}, for more information
-about the page address@hidden
+about the page commands.
@node Updating Nodes and Menus
@section Updating Nodes and Menus
@@ -2180,7 +2180,7 @@
and to create menus in a file that has none.
If you do not use the updating commands, you need to write menus and
-node pointers by hand, which is a tedious address@hidden
+node pointers by hand, which is a tedious task.
@menu
* Updating Commands:: Five major updating commands.
@@ -2194,22 +2194,21 @@
@node Updating Commands
@subsection The Updating Commands
-You can use the updating commands to:@refill
+You can use the updating commands to:
@itemize @bullet
@item
-insert or update the `Next', `Previous', and `Up' pointers of a
-node,@refill
+insert or update the `Next', `Previous', and `Up' pointers of a node,
@item
-insert or update the menu for a section, address@hidden
+insert or update the menu for a section, and
@item
-create a master menu for a Texinfo source address@hidden
+create a master menu for a Texinfo source file.
@end itemize
You can also use the commands to update all the nodes and menus in a
-region or in a whole Texinfo address@hidden
+region or in a whole Texinfo file.
The updating commands work only with conventional Texinfo files, which
are structured hierarchically like books. In such files, a structuring
@@ -2237,16 +2236,16 @@
files since they do not refer to nodes within the current buffer. This
is a deficiency. Rather than use menu entries, you can use cross
references to refer to other Info files. None of the updating commands
-affect cross address@hidden
+affect cross references.
Texinfo mode has five updating commands that are used most often: two
are for updating the node pointers or menu of a single node (or a
region); two are for updating every node pointer and menu in a file;
and one, the @code{texinfo-master-menu} command, is for creating a
master menu for a complete file, and optionally, for updating every
-node and menu in the whole Texinfo address@hidden
+node and menu in the whole Texinfo file.
-The @code{texinfo-master-menu} command is the primary command:@refill
+The @code{texinfo-master-menu} command is the primary command:
@table @kbd
@item C-c C-u m
@@ -2254,15 +2253,15 @@
@findex texinfo-master-menu
Create or update a master menu that includes all the other menus
(incorporating the descriptions from pre-existing menus, if
-any)address@hidden
+any).
With an argument (prefix argument, @kbd{C-u,} if interactive), first create or
update all the nodes and all the regular menus in the buffer before
constructing the master menu. (@xref{The Top Node, , The Top Node and
-Master Menu}, for more about a master menu.)@refill
+Master Menu}, for more about a master menu.)
For @code{texinfo-master-menu} to work, the Texinfo file must have a
-`Top' node and at least one subsequent address@hidden
+`Top' node and at least one subsequent node.
After extensively editing a Texinfo file, you can type the following:
@@ -2273,15 +2272,15 @@
@end example
@noindent
-This updates all the nodes and menus completely and all at address@hidden
+This updates all the nodes and menus completely and all at once.
@end table
The other major updating commands do smaller jobs and are designed for
the person who updates nodes and menus as he or she writes a Texinfo
address@hidden
+file.
@need 1000
-The commands are:@refill
+The commands are:
@table @kbd
@item C-c C-u C-n
@@ -2293,7 +2292,7 @@
pointers in it, the old pointers are removed and new ones inserted.
With an argument (prefix argument, @kbd{C-u}, if interactive), this command
updates all @code{@@node} lines in the region (which is the text
-between point and mark)address@hidden
+between point and mark).
@item C-c C-u C-m
@itemx M-x texinfo-make-menu
@@ -2302,19 +2301,19 @@
With an argument (@kbd{C-u} as prefix argument, if
interactive), the command makes or updates menus for the
nodes which are either within or a part of the
address@hidden
+region.
Whenever @code{texinfo-make-menu} updates an existing menu, the
descriptions from that menu are incorporated into the new menu. This
is done by copying descriptions from the existing menu to the entries
in the new menu that have the same node names. If the node names are
-different, the descriptions are not copied to the new address@hidden
+different, the descriptions are not copied to the new menu.
@item C-c C-u C-e
@itemx M-x texinfo-every-node-update
@findex texinfo-every-node-update
Insert or update the `Next', `Previous', and `Up' pointers for every
-node in the address@hidden
+node in the buffer.
@item C-c C-u C-a
@itemx M-x texinfo-all-menus-update
@@ -2322,12 +2321,12 @@
Create or update all the menus in the buffer. With an argument
(@kbd{C-u} as prefix argument, if interactive), first insert
or update all the node
-pointers before working on the address@hidden
+pointers before working on the menus.
If a master menu exists, the @code{texinfo-all-menus-update} command
updates it; but the command does not create a new master menu if none
already exists. (Use the @code{texinfo-master-menu} command for
-that.)@refill
+that.)
When working on a document that does not merit a master menu, you can
type the following:
@@ -2339,7 +2338,7 @@
@end example
@noindent
-This updates all the nodes and address@hidden
+This updates all the nodes and menus.
@end table
The @code{texinfo-column-for-description} variable specifies the
@@ -2354,7 +2353,7 @@
indent existing menu descriptions to a specified column. Finally, if
you wish, you can use the @code{texinfo-insert-node-lines} command to
insert missing @code{@@node} lines into a file. (@xref{Other Updating
-Commands}, for more information.)@refill
+Commands}, for more information.)
@node Updating Requirements
@subsection Updating Requirements
@@ -2368,12 +2367,12 @@
chapter, but not with a section; you can follow a chapter with a
section, but not with a subsection. However, you may `jump up' any
number of levels at one time---for example, from a subsection to a
address@hidden
+chapter.
Each @code{@@node} line, with the exception of the line for the `Top'
node, must be followed by a line with a structuring command such as
@code{@@chapter}, @code{@@section}, or
address@hidden@@address@hidden
address@hidden@@unnumberedsubsec}.
Each @code{@@node} line/structuring-command line combination
must look either like this:
@@ -2416,7 +2415,7 @@
The menu updating commands create a menu of sections within a chapter,
a menu of subsections within a section, and so on. This means that
-you must have a `Top' node if you want a menu of address@hidden
+you must have a `Top' node if you want a menu of chapters.
Incidentally, the @code{makeinfo} command will create an Info file for a
hierarchically organized Texinfo file that lacks `Next', `Previous' and
@@ -2432,14 +2431,14 @@
@subsection Other Updating Commands
In addition to the five major updating commands, Texinfo mode
-possesses several less frequently used updating commands:@refill
+possesses several less frequently used updating commands:
@table @kbd
@item M-x texinfo-insert-node-lines
@findex texinfo-insert-node-lines
Insert @code{@@node} lines before the @code{@@chapter},
@code{@@section}, and other sectioning commands wherever they are
-missing throughout a region in a Texinfo address@hidden
+missing throughout a region in a Texinfo file.
With an argument (@kbd{C-u} as prefix argument, if interactive), the
@code{texinfo-insert-node-lines} command not only inserts
@@ -2447,10 +2446,10 @@
the names of the corresponding nodes. In addition, it inserts the
titles as node names in pre-existing @code{@@node} lines that lack
names. Since node names should be more concise than section or
-chapter titles, you must manually edit node names so address@hidden
+chapter titles, you must manually edit node names so inserted.
For example, the following marks a whole buffer as a region and inserts
address@hidden@@node} lines and titles throughout:@refill
address@hidden@@node} lines and titles throughout:
@example
C-x h C-u M-x texinfo-insert-node-lines
@@ -2481,7 +2480,7 @@
interactive), the @code{texinfo-indent-menu-description} command indents
every description in every menu in the region. However, this command
does not indent the second and subsequent lines of a multi-line
address@hidden
+description.
@item M-x texinfo-sequential-node-update
@findex texinfo-sequential-node-update
@@ -2494,7 +2493,7 @@
you look through the file sequentially, so sequentially ordered nodes
are not strictly necessary.) With an argument (prefix argument, if
interactive), the @code{texinfo-sequential-node-update} command
-sequentially updates all the nodes in the address@hidden
+sequentially updates all the nodes in the region.
@end table
@node Info Formatting
@@ -2505,10 +2504,10 @@
Texinfo mode provides several commands for formatting part or all of a
Texinfo file for Info. Often, when you are writing a document, you
-want to format only part of a file---that is, a address@hidden
+want to format only part of a file---that is, a region.
You can use either the @code{texinfo-format-region} or the
address@hidden command to format a region:@refill
address@hidden command to format a region:
@table @kbd
@findex texinfo-format-region
@@ -2516,11 +2515,11 @@
@itemx M-x texinfo-format-region
@itemx C-c C-m C-r
@itemx M-x makeinfo-region
-Format the current region for address@hidden
+Format the current region for Info.
@end table
You can use either the @code{texinfo-format-buffer} or the
address@hidden command to format a whole buffer:@refill
address@hidden command to format a whole buffer:
@table @kbd
@findex texinfo-format-buffer
@@ -2528,7 +2527,7 @@
@itemx M-x texinfo-format-buffer
@itemx C-c C-m C-b
@itemx M-x makeinfo-buffer
-Format the current buffer for address@hidden
+Format the current buffer for Info.
@end table
@need 1000
@@ -2553,7 +2552,7 @@
For @TeX{} or the Info formatting commands to work, the file @emph{must}
include a line that has @code{@@setfilename} in its header.
address@hidden an Info File}, for details about Info address@hidden
address@hidden an Info File}, for details about Info formatting.
@node Printing
@comment node-name, next, previous, up
@@ -2576,7 +2575,7 @@
only part of a file to see what it will look like. You can use the
@code{texinfo-tex-region} and related commands for this purpose. Use
the @code{texinfo-tex-buffer} command to format all of a
address@hidden
+buffer.
@table @kbd
@item C-c C-t C-b
@@ -2584,12 +2583,12 @@
@findex texinfo-tex-buffer
Run @code{texi2dvi} on the buffer. In addition to running @TeX{} on the
buffer, this command automatically creates or updates indices as
address@hidden
+needed.
@item C-c C-t C-r
@itemx M-x texinfo-tex-region
@findex texinfo-tex-region
-Run @TeX{} on the address@hidden
+Run @TeX{} on the region.
@item C-c C-t C-i
@itemx M-x texinfo-texindex
@@ -2600,13 +2599,13 @@
a second time after sorting the raw index files with the @code{texindex}
command. (Usually, you do not format an index when you format a region,
only when you format a buffer. Now that the @code{texi2dvi} command
-exists, there is little or no need for this command.)@refill
+exists, there is little or no need for this command.)
@item C-c C-t C-p
@itemx M-x texinfo-tex-print
@findex texinfo-tex-print
Print the file (or the part of the file) previously formatted with
address@hidden or @address@hidden
address@hidden or @code{texinfo-tex-region}.
@end table
For @code{texinfo-tex-region} or @code{texinfo-tex-buffer} to work, the
@@ -2614,10 +2613,10 @@
include an @code{@@settitle} line. The file must end with @code{@@bye}
on a line by itself. (When you use @code{texinfo-tex-region}, you must
surround the @code{@@settitle} line with start-of-header and
-end-of-header lines.)@refill
+end-of-header lines.)
@xref{Hardcopy}, for a description of the other @TeX{} related
-commands, such as @address@hidden
+commands, such as @code{tex-show-print-queue}.
@node Texinfo Mode Summary
@section Texinfo Mode Summary
@@ -2625,14 +2624,14 @@
In Texinfo mode, each set of commands has default keybindings that
begin with the same keys. All the commands that are custom-created
for Texinfo mode begin with @kbd{C-c}. The keys are somewhat
address@hidden
+mnemonic.
@subheading Insert Commands
The insert commands are invoked by typing @kbd{C-c} twice and then the
first letter of the @@-command to be inserted. (It might make more
sense mnemonically to use @kbd{C-c C-i}, for `custom insert', but
address@hidden C-c} is quick to type.)@refill
address@hidden C-c} is quick to type.)
@example
C-c C-c c @r{Insert} @samp{@@code}.
@@ -2656,7 +2655,7 @@
@subheading Show Structure
The @code{texinfo-show-structure} command is often used within a
-narrowed address@hidden
+narrowed region.
@example
C-c C-s @r{List all the headings.}
@@ -2665,7 +2664,7 @@
@subheading The Master Update Command
The @code{texinfo-master-menu} command creates a master menu; and can
-be used to update every node and menu in a file as address@hidden
+be used to update every node and menu in a file as well.
@c Probably should use @tables in this section.
@example
@@ -2686,7 +2685,7 @@
The update pointer commands are invoked by typing @kbd{C-c C-u} and
then either @kbd{C-n} for @code{texinfo-update-node} or @kbd{C-e} for
address@hidden@refill
address@hidden
@example
C-c C-u C-n @r{Update a node.}
@@ -2699,7 +2698,7 @@
and then either @kbd{C-m} for @code{texinfo-make-menu} or
@kbd{C-a} for @code{texinfo-all-menus-update}. To update
both nodes and menus at the same time, precede @kbd{C-c C-u
-C-a} with @address@hidden
+C-a} with @kbd{C-u}.
@example
C-c C-u C-m @r{Make or update a menu.}
@@ -2720,11 +2719,11 @@
The Info formatting commands that are written in Emacs Lisp are
invoked by typing @kbd{C-c C-e} and then either @kbd{C-r} for a region
-or @kbd{C-b} for the whole address@hidden
+or @kbd{C-b} for the whole buffer.
The Info formatting commands that are written in C and based on the
@code{makeinfo} program are invoked by typing @kbd{C-c C-m} and then
-either @kbd{C-r} for a region or @kbd{C-b} for the whole address@hidden
+either @kbd{C-r} for a region or @kbd{C-b} for the whole buffer.
@need 800
@noindent
@@ -2753,7 +2752,7 @@
The @TeX{} typesetting and printing commands are invoked by typing
@kbd{C-c C-t} and then another control command: @kbd{C-r} for
@code{texinfo-tex-region}, @kbd{C-b} for @code{texinfo-tex-buffer},
-and so address@hidden
+and so on.
@example
C-c C-t C-r @r{Run @TeX{} on the region.}
@@ -3634,7 +3633,7 @@
headings from being generated or to start them for either single or
double-sided printing. (Write an @code{@@headings} command immediately
after the @code{@@end titlepage} command. @xref{headings on off, , The
address@hidden@@headings} Command}, for more information.)@refill
address@hidden@@headings} Command}, for more information.)
@item
Or, you may specify your own page heading and footing format.
@@ -4353,7 +4352,7 @@
chapters, sections, subsections, and subsubsections. These commands
generate large headings; they also provide information for the table
of contents of a printed manual (@pxref{Contents, , Generating a Table
-of Contents})address@hidden
+of Contents}).
The chapter structuring commands do not create an Info node structure,
so normally you should put an @code{@@node} command immediately before
@@ -4361,12 +4360,12 @@
are likely to use the chapter structuring commands without using the
node structuring commands is if you are writing a document that
contains no cross references and will never be transformed into Info
address@hidden
+format.
It is unlikely that you will ever write a Texinfo file that is
intended only as an Info file and not as a printable document. If you
do, you might still use chapter structuring commands to create a
-heading at the top of each node---but you don't need address@hidden
+heading at the top of each node---but you don't need to.
@menu
* Tree Structuring:: A manual is like an upside down tree @dots{}
@@ -4393,10 +4392,10 @@
sections, subsections, and the like. This structure can be visualized
as a tree (or rather as an upside-down tree) with the root at the top
and the levels corresponding to chapters, sections, subsection, and
address@hidden
+subsubsections.
Here is a diagram that shows a Texinfo file with three chapters,
-each of which has two address@hidden
+each of which has two sections.
@example
@group
@@ -4415,7 +4414,7 @@
@end example
In a Texinfo file that has this structure, the beginning of Chapter 2
-looks like this:@refill
+looks like this:
@example
@group
@@ -4426,7 +4425,7 @@
The chapter structuring commands are described in the sections that
follow; the @code{@@node} and @code{@@menu} commands are described in
-following chapters. (@xref{Nodes}, and see @ref{Menus}.)@refill
+following chapters. (@xref{Nodes}, and see @ref{Menus}.)
@node Structuring Command Types
@@ -4435,22 +4434,22 @@
The chapter structuring commands fall into four groups or series, each
of which contains structuring commands corresponding to the
hierarchical levels of chapters, sections, subsections, and
address@hidden
+subsubsections.
The four groups are the @code{@@chapter} series, the
@code{@@unnumbered} series, the @code{@@appendix} series, and the
address@hidden@@heading} address@hidden
address@hidden@@heading} series.
Each command produces titles that have a different appearance on the
printed page or Info file; only some of the commands produce
titles that are listed in the table of contents of a printed book or
address@hidden
+manual.
@itemize @bullet
@item
The @code{@@chapter} and @code{@@appendix} series of commands produce
numbered or lettered entries both in the body of a printed work and in
-its table of address@hidden
+its table of contents.
@item
The @code{@@unnumbered} series of commands produce unnumbered entries
@@ -4475,7 +4474,7 @@
When an @code{@@setchapternewpage} command says to do so, the
@code{@@chapter}, @code{@@unnumbered}, and @code{@@appendix} commands
start new pages in the printed manual; the @code{@@heading} commands
-do address@hidden
+do not.
@end itemize
Here are the four groups of chapter structuring commands:
@@ -4527,10 +4526,10 @@
@code{@@chapter} identifies a chapter in the document. Write the
command at the beginning of a line and follow it on the same line by
-the title of the address@hidden
+the title of the chapter.
For example, this chapter in this manual is entitled ``Chapter
-Structuring''; the @code{@@chapter} line looks like this:@refill
+Structuring''; the @code{@@chapter} line looks like this:
@example
@@chapter Chapter Structuring
@@ -4538,11 +4537,11 @@
In @TeX{}, the @code{@@chapter} command creates a chapter in the
document, specifying the chapter title. The chapter is numbered
address@hidden
+automatically.
In Info, the @code{@@chapter} command causes the title to appear on a
line by itself, with a line of asterisks inserted underneath. Thus,
-in Info, the above example produces the following output:@refill
+in Info, the above example produces the following output:
@example
Chapter Structuring
@@ -4577,11 +4576,11 @@
@findex chapheading
The @code{@@majorheading} and @code{@@chapheading} commands put
-chapter-like headings in the body of a address@hidden
+chapter-like headings in the body of a document.
However, neither command causes @TeX{} to produce a numbered heading
or an entry in the table of contents; and neither command causes
address@hidden to start a new page in a printed address@hidden
address@hidden to start a new page in a printed manual.
In @TeX{}, an @code{@@majorheading} command generates a larger vertical
whitespace before the heading than an @code{@@chapheading} command but
@@ -4591,7 +4590,7 @@
the @code{@@majorheading} and
@code{@@chapheading} commands are equivalent to
@code{@@chapter}: the title is printed on a line by itself with a line
-of asterisks underneath. (@xref{chapter, , @code{@@chapter}}.)@refill
+of asterisks underneath. (@xref{chapter, , @code{@@chapter}}.)
@node section
@@ -4649,20 +4648,20 @@
@item @@unnumberedsec
The @code{@@unnumberedsec} command may be used within an
unnumbered chapter or within a regular chapter or appendix to
-provide an unnumbered address@hidden
+provide an unnumbered section.
@item @@appendixsec
@itemx @@appendixsection
@code{@@appendixsection} is a longer spelling of the
address@hidden@@appendixsec} command; the two are address@hidden
address@hidden@@appendixsec} command; the two are synonymous.
@findex appendixsection
Conventionally, the @code{@@appendixsec} or @code{@@appendixsection}
-command is used only within address@hidden
+command is used only within appendices.
@item @@heading
You may use the @code{@@heading} command anywhere you wish for a
-section-style heading that will not appear in the table of address@hidden
+section-style heading that will not appear in the table of contents.
@end table
@code{@@unnumberedsec} and @code{@@appendixsec} do not need to be used
@@ -4694,7 +4693,7 @@
@end example
In a printed manual, subsections are listed in the table of contents
-and are numbered three levels address@hidden
+and are numbered three levels deep.
@node unnumberedsubsec appendixsubsec subheading
@@ -5703,7 +5702,7 @@
@cindex Menu example
@cindex Example menu
-A menu looks like this in Texinfo:@refill
+A menu looks like this in Texinfo:
@example
@group
@@ -5728,7 +5727,7 @@
@end example
@need 700
-Here is an example as you might see it in a Texinfo file:@refill
+Here is an example as you might see it in a Texinfo file:
@example
@group
@@ -5761,11 +5760,11 @@
entry name and the name of the node referred to by that name.
@samp{Multiples} is the menu entry name; it refers to the node named
@samp{Buffers}. The line @samp{Larger Units of Text} is a comment; it
-appears in the menu, but is not an address@hidden
+appears in the menu, but is not an entry.
Since no file name is specified with either @samp{Files} or
@samp{Buffers}, they must be the names of nodes in the same Info file
-(@pxref{Other Info Files, , Referring to Other Info Files})address@hidden
+(@pxref{Other Info Files, , Referring to Other Info Files}).
@node Other Info Files
@section Referring to Other Info Files
@@ -5779,10 +5778,10 @@
node in another Info file by writing the file name in parentheses just
before the node name. In this case, you should use the three-part menu
entry format, which saves the reader from having to type the file
address@hidden
+name.
@need 800
-The format looks like this:@refill
+The format looks like this:
@example
@group
@@ -5795,7 +5794,7 @@
For example, to refer directly to the @samp{Outlining} and
@samp{Rebinding} nodes in the @cite{Emacs Manual}, you would write a
-menu like this:@refill
+menu like this:
@example
@group
@@ -5809,7 +5808,7 @@
@end example
If you do not list the node name, but only name the file, then Info
-presumes that you are referring to the `Top' address@hidden
+presumes that you are referring to the `Top' node.
The @file{dir} file that contains the main menu for Info has menu
entries that list only file names. These take you directly to the `Top'
@@ -5829,7 +5828,7 @@
@noindent
(The @file{dir} top level directory for the Info system is an Info file,
not a Texinfo file, but a menu entry looks the same in both types of
-file.)@refill
+file.)
The GNU Emacs Texinfo mode menu updating commands only work with nodes
within the current buffer, so you cannot use them to create menus that
@@ -7008,7 +7007,7 @@
labelled by commands that tell what kind of object they are, it is easy
to change the way the Texinfo formatters prepare such text. (Texinfo is
an @emph{intentional} formatting language rather than a @emph{typesetting}
-formatting language.)@refill
+formatting language.)
For example, in a printed manual,
code is usually illustrated in a typewriter font;
@@ -7018,7 +7017,7 @@
highlighted. If straight typesetting commands were used in the body
of the file and you wanted to make a change, you would need to check
every single occurrence to make sure that you were changing code and
-not something else that should not be address@hidden
+not something else that should not be changed.
@menu
* Useful Highlighting:: Highlighting provides useful information.
@@ -7049,9 +7048,9 @@
macro) to insert an index entry after every paragraph that contains
words or phrases marked by a specified command. You could do this to
construct an index of functions if you had not already made the
address@hidden
+entries.
-The commands serve a variety of purposes:@refill
+The commands serve a variety of purposes:
@table @code
@item @@address@hidden@address@hidden
@@ -7314,7 +7313,7 @@
(Also, this example shows that you can add spaces for clarity. If you
explicitly want to mention a space character as one of the characters of
-input, write @kbd{@@address@hidden@}} for it.)@refill
+input, write @kbd{@@address@hidden@}} for it.)
@node key
@@ -7322,7 +7321,7 @@
@findex key
Use the @code{@@key} command for the conventional name for a key on a
-keyboard, as in:@refill
+keyboard, as in:
@example
@@address@hidden@}
@@ -7330,7 +7329,7 @@
You can use the @code{@@key} command within the argument of an
@code{@@kbd} command when the sequence of characters to be typed
-includes one or more keys that are described by address@hidden
+includes one or more keys that are described by name.
For example, to produce @kbd{C-x @key{ESC}} and @address@hidden you
would type:
@@ -7393,7 +7392,7 @@
or `sample' of a sequence of characters in a file, string, pattern, etc.
Enclose the text in braces. The argument appears within single
quotation marks in both the Info file and the printed manual; in
-addition, it is printed in a fixed-width address@hidden
+addition, it is printed in a fixed-width font.
@example
To match @@address@hidden@} at the end of the line,
@@ -7405,7 +7404,7 @@
@quotation
To match @samp{foo} at the end of the line, use the regexp
address@hidden@refill
address@hidden
@end quotation
Any time you are referring to single characters, you should use
@@ -7413,13 +7412,13 @@
Also, you may use @code{@@samp} for entire statements in C and for entire
shell commands---in this case, @code{@@samp} often looks better than
@code{@@code}. Basically, @code{@@samp} is a catchall for whatever is
-not covered by @code{@@code}, @code{@@kbd}, or @code{@@address@hidden
+not covered by @code{@@code}, @code{@@kbd}, or @code{@@key}.
Only include punctuation marks within braces if they are part of the
string you are specifying. Write punctuation marks outside the braces
if those punctuation marks are part of the English text that surrounds
the string. In the following sentence, for example, the commas and
-period are outside of the braces:@refill
+period are outside of the braces:
@example
@group
@@ -7489,7 +7488,7 @@
@dfn{metasyntactic variable} is something that stands for another piece of
text. For example, you should use a metasyntactic variable in the
documentation of a function to describe the arguments that are passed
-to that address@hidden
+to that function.
Do not use @code{@@var} for the names of particular variables in
programming languages. These are specific names from a program, so
@@ -7521,12 +7520,12 @@
@noindent
(Note that @code{@@var} may appear inside @code{@@code},
address@hidden@@samp}, @code{@@file}, etc.)@refill
address@hidden@@samp}, @code{@@file}, etc.)
Write a metasyntactic variable all in lower case without spaces, and
use hyphens to make it more readable. Thus, the Texinfo source for
the illustration of how to begin a Texinfo manual looks like
-this:@refill
+this:
@example
@group
@@ -7548,7 +7547,7 @@
@end example
In some documentation styles, metasyntactic variables are shown with
-angle brackets, for example:@refill
+angle brackets, for example:
@example
@dots{}, type rm <filename>
@@ -7557,7 +7556,7 @@
@noindent
However, that is not the style that Texinfo uses. (You can, of
course, modify the sources to @file{texinfo.tex} and the Info formatting
commands
-to output the @code{<@dots{}>} format if you wish.)@refill
+to output the @code{<@dots{}>} format if you wish.)
@node env
@@ -7591,7 +7590,7 @@
for symbols in a programming language; use @code{@@code}.
Currently, @code{@@file} is equivalent to @code{@@samp} in its effects.
-For example,@refill
+For example,
@example
The @@address@hidden@} files are in
@@ -7667,7 +7666,7 @@
reader ought to know. Mere passing mention of a term for the first
time does not deserve @code{@@dfn}. The command generates italics in
the printed manual, and double quotation marks in the Info file. For
-example:@refill
+example:
@example
Getting rid of a file is called @@address@hidden@} it.
@@ -7913,7 +7912,7 @@
category. Texinfo has two commands to do this. Also, Texinfo has
several commands that specify the font in which @TeX{} will typeset
text. These commands have no effect on Info and only one of them,
-the @code{@@r} command, has any regular address@hidden
+the @code{@@r} command, has any regular use.
@menu
* emph & strong:: How to emphasize text in Texinfo.
@@ -8605,9 +8604,9 @@
The command is written at the beginning of a line and applies only to
the text that follows the command that is on the same line. Do not use
braces around the text. In a printed manual, the text on an
address@hidden@@exdent} line is printed in the roman address@hidden
address@hidden@@exdent} line is printed in the roman font.
address@hidden@@exdent} is usually used within examples. Thus,@refill
address@hidden@@exdent} is usually used within examples. Thus,
@example
@group
@@ -8634,7 +8633,7 @@
In practice, the @code{@@exdent} command is rarely used.
Usually, you un-indent text by ending the example and
-returning the page to its normal address@hidden
+returning the page to its normal width.
@node flushleft & flushright
@@ -8649,7 +8648,7 @@
but do not fill the text. The commands are written on lines of their
own, without braces. The @code{@@flushleft} and @code{@@flushright}
commands are ended by @code{@@end flushleft} and @code{@@end
-flushright} commands on lines of their address@hidden
+flushright} commands on lines of their own.
@need 1500
For example,
@@ -8901,27 +8900,27 @@
Texinfo automatically indents the text in lists or tables, and numbers
an enumerated list. This last feature is useful if you modify the
-list, since you do not need to renumber it address@hidden
+list, since you do not need to renumber it yourself.
Numbered lists and tables begin with the appropriate @@-command at the
beginning of a line, and end with the corresponding @code{@@end}
command on a line by itself. The table and itemized-list commands
also require that you write formatting information on the same line as
-the beginning @@address@hidden
+the beginning @@-command.
Begin an enumerated list, for example, with an @code{@@enumerate}
command and end the list with an @code{@@end enumerate} command.
Begin an itemized list with an @code{@@itemize} command, followed on
the same line by a formatting command such as @code{@@bullet}, and end
-the list with an @code{@@end itemize} address@hidden
+the list with an @code{@@end itemize} command.
@findex end
Precede each element of a list with an @code{@@item} or @code{@@itemx}
address@hidden
+command.
@sp 1
@noindent
-Here is an itemized list of the different kinds of table and lists:@refill
+Here is an itemized list of the different kinds of table and lists:
@itemize @bullet
@item
@@ -8936,7 +8935,7 @@
@sp 1
@noindent
-Here is an enumerated list with the same items:@refill
+Here is an enumerated list with the same items:
@enumerate
@item
@@ -8952,7 +8951,7 @@
@sp 1
@noindent
And here is a two-column table with the same items and their
address@hidden@@-commands}:@refill
address@hidden@@-commands}:
@table @code
@item @@itemize
@@ -8975,7 +8974,7 @@
The @code{@@itemize} command produces sequences of indented
paragraphs, with a bullet or other mark inside the left margin
-at the beginning of each paragraph for which such a mark is address@hidden
+at the beginning of each paragraph for which such a mark is desired.
@cindex @code{@@w}, for blank items
Begin an itemized list by writing @code{@@itemize} at the beginning of
@@ -9001,7 +9000,7 @@
Usually, you should put a blank line before an @code{@@item}. This
puts a blank line in the Info file. (@TeX{} inserts the proper
interline whitespace in either case.) Except when the entries are
-very brief, these blank lines make the list look address@hidden
+very brief, these blank lines make the list look better.
Here is an example of the use of @code{@@itemize}, followed by the
output it produces. @code{@@bullet} produces an @samp{*} in Info and a
@@ -9035,7 +9034,7 @@
@end quotation
Itemized lists may be embedded within other itemized lists. Here is a
-list marked with dashes embedded in a list marked with bullets:@refill
+list marked with dashes embedded in a list marked with bullets:
@example
@group
@@ -9130,7 +9129,7 @@
Proximate causes.
@end enumerate
@sp 1
-Here is an example with an argument of @kbd{3}:@refill
+Here is an example with an argument of @kbd{3}:
@sp 1
@example
@group
@@ -9162,38 +9161,38 @@
@end enumerate
@sp 1
Here is a brief summary of the alternatives. The summary is constructed
-using @code{@@enumerate} with an argument of @address@hidden
+using @code{@@enumerate} with an argument of @kbd{a}.
@sp 1
@enumerate a
@item
@code{@@enumerate}
Without an argument, produce a numbered list, starting with the number
address@hidden
+1.
@item
@code{@@enumerate @var{positive-integer}}
With a (positive) numeric argument, start a numbered list with that
number. You can use this to continue a list that you interrupted with
-other address@hidden
+other text.
@item
@code{@@enumerate @var{upper-case-letter}}
With an upper case letter as argument, start a list
in which each item is marked
-by a letter, beginning with that upper case address@hidden
+by a letter, beginning with that upper case letter.
@item
@code{@@enumerate @var{lower-case-letter}}
With a lower case letter as argument, start a list
in which each item is marked by
-a letter, beginning with that lower case address@hidden
+a letter, beginning with that lower case letter.
@end enumerate
-You can also nest enumerated lists, as in an address@hidden
+You can also nest enumerated lists, as in an outline.
@node Two-column Tables
@section Making a Two-column Table
@@ -9307,7 +9306,7 @@
simplifies the task of creating indices. Only the items on the same
line as the @code{@@item} commands are indexed, and they are indexed in
exactly the form that they appear on that line. @xref{Indices},
-for more information about address@hidden
+for more information about indices.
Begin a two-column table using @code{@@ftable} or @code{@@vtable} by
writing the @@-command at the beginning of a line, followed on the same
@@ -9358,12 +9357,12 @@
@itemx downcase
These two functions accept a character or a string as
argument, and return the corresponding upper case (lower
-case) character or address@hidden
+case) character or string.
@end table
@noindent
(Note also that this example illustrates multi-line supporting text in
-a two-column table.)@refill
+a two-column table.)
@node Multi-column Tables
@@ -10329,7 +10328,7 @@
The @code{@@syncodeindex} command takes two arguments; they are the name
of the index to redirect, and the name of the index to redirect it to.
-The template looks like this:@refill
+The template looks like this:
@example
@@syncodeindex @var{from} @var{to}
@@ -10339,7 +10338,7 @@
@cindex Two letter names for indices
@cindex Indices, two letter names
@cindex Names for indices
-For this purpose, the indices are given two-letter names:@refill
+For this purpose, the indices are given two-letter names:
@table @samp
@item cp
@@ -10359,7 +10358,7 @@
Write an @code{@@syncodeindex} command before or shortly after the
end-of-header line at the beginning of a Texinfo file. For example,
to merge a function index with a concept index, write the
-following:@refill
+following:
@example
@@syncodeindex fn cp
@@ -10367,10 +10366,10 @@
@noindent
This will cause all entries designated for the function index to merge
-in with the concept index address@hidden
+in with the concept index instead.
To merge both a variables index and a function index into a concept
-index, write the following:@refill
+index, write the following:
@example
@group
@@ -10385,7 +10384,7 @@
whatever default font is used by the index to which the entries are
now directed. This way, if you direct function names from a function
index into a concept index, all the function names are printed in the
address@hidden@@code} font as you would address@hidden
address@hidden@@code} font as you would expect.
@node synindex
@@ -10396,10 +10395,10 @@
@code{@@syncodeindex} command, except that it does not put the
`from' index entries into the @code{@@code} font; rather it puts
them in the roman font. Thus, you use @code{@@synindex} when you
-merge a concept index into a function address@hidden
+merge a concept index into a function index.
@xref{Printing Indices & Menus}, for information about printing an index
-at the end of a book or creating an index menu in an Info address@hidden
+at the end of a book or creating an index menu in an Info file.
@node New Indices
@@ -11709,7 +11708,7 @@
The glyph-insertion commands do not need to be used within an example, but
most often they are. Every glyph-insertion command is followed by a pair of
-left- and right-hand address@hidden
+left- and right-hand braces.
@menu
* Glyphs Summary::
@@ -11725,7 +11724,7 @@
@node Glyphs Summary
@subsection Glyphs Summary
-Here are the different glyph commands:@refill
+Here are the different glyph commands:
@table @asis
@item @result{}
@@ -11757,7 +11756,7 @@
@findex result
Use the @code{@@address@hidden@}} command to indicate the result of
-evaluating an address@hidden
+evaluating an expression.
@iftex
The @code{@@address@hidden@}} command is displayed as @address@hidden in
@@ -11787,7 +11786,7 @@
When an expression is a macro call, it expands into a new expression.
You can indicate the result of the expansion with the
address@hidden@@address@hidden@}} address@hidden
address@hidden@@address@hidden@}} command.
@iftex
The @code{@@address@hidden@}} command is displayed as @address@hidden
@@ -11842,7 +11841,7 @@
@findex print
Sometimes an expression will print output during its execution. You
-can indicate the printed output with the @code{@@address@hidden@}}
address@hidden
+can indicate the printed output with the @code{@@address@hidden@}} command.
@iftex
The @code{@@address@hidden@}} command is displayed as @samp{-|} in Info and
@@ -11888,7 +11887,7 @@
@findex error
A piece of code may cause an error when you evaluate it. You can
-designate the error message with the @code{@@address@hidden@}} address@hidden
+designate the error message with the @code{@@address@hidden@}} command.
@iftex
The @code{@@address@hidden@}} command is displayed as @samp{error-->} in Info
@@ -11934,7 +11933,7 @@
@findex equiv
Sometimes two expressions produce identical results. You can indicate the
-exact equivalence of two forms with the @code{@@address@hidden@}}
address@hidden
+exact equivalence of two forms with the @code{@@address@hidden@}} command.
@iftex
The @code{@@address@hidden@}} command is displayed as @samp{==} in Info and
@@ -11974,12 +11973,12 @@
Sometimes you need to show an example of text in an Emacs buffer. In
such examples, the convention is to include the entire contents of the
buffer in question between two lines of dashes containing the buffer
address@hidden
+name.
You can use the @samp{@@address@hidden@}} command to show the location of point
in the text in the buffer. (The symbol for point, of course, is not
part of the text in the buffer; it indicates the place @emph{between}
-two characters where point is located.)@refill
+two characters where point is located.)
@iftex
The @code{@@address@hidden@}} command is displayed as @samp{-!-} in Info and
@@ -11992,7 +11991,7 @@
@end ifnottex
The following example shows the contents of buffer @file{foo} before
-and after evaluating a Lisp command to insert the word @address@hidden
+and after evaluating a Lisp command to insert the word @code{changed}.
@example
@group
@@ -12014,7 +12013,7 @@
@end group
@end example
-In a Texinfo source file, the example is written like this:@refill
+In a Texinfo source file, the example is written like this:
@example
@@example
@@ -12340,7 +12339,7 @@
@noindent
generates two blank lines.
-The @code{@@sp} command is most often used in the title address@hidden
+The @code{@@sp} command is most often used in the title page.
@ignore
@c node br, page, sp, Breaks
@@ -12353,7 +12352,7 @@
line. You can use the command within or at the end of a line. If
used within a line, the @code{@@address@hidden@}} command must be followed by
left and right braces (as shown here) to mark the end of the
address@hidden
+command.
@need 700
For example,
@@ -12406,7 +12405,7 @@
group, which will appear entirely on one page in the printed output.
The group is terminated by a line containing only @code{@@end group}.
These two lines produce no output of their own, and in the Info file
-output they have no effect at address@hidden
+output they have no effect at all.
@c Once said that these environments
@c turn off vertical spacing between ``paragraphs''.
@@ -12418,7 +12417,7 @@
@xref{Quotations and Examples}. (What all these commands have in
common is that each line of input produces a line of output.) In
other contexts, @code{@@group} can cause anomalous vertical
address@hidden
+spacing.
@need 750
This formatting requirement means that you should write:
@@ -12448,7 +12447,7 @@
not start to generate error messages until it has processed
considerable text. It is a good rule of thumb to look for a missing
@code{@@end group} if you get incomprehensible error messages in
address@hidden@refill
address@hidden
@node need
@section @code{@@need @var{mils}}: Prevent Page Breaks
@@ -12459,12 +12458,12 @@
a new page in a printed manual if fewer than @var{n} mils (thousandths
of an inch) remain on the current page. Do not use
braces around the argument @var{n}. The @code{@@need} command has no
-effect on Info files since they are not address@hidden
+effect on Info files since they are not paginated.
@need 800
This paragraph is preceded by an @code{@@need} command that tells
@TeX{} to start a new page if fewer than 800 mils (eight-tenths
-inch) remain on the page. It looks like this:@refill
+inch) remain on the page. It looks like this:
@example
@group
@@ -12474,7 +12473,7 @@
@end example
The @code{@@need} command is useful for preventing orphans (single
-lines at the bottoms of printed pages)address@hidden
+lines at the bottoms of printed pages).
@node Definition Commands
@@ -12484,7 +12483,7 @@
The @code{@@deffn} command and the other @dfn{definition commands}
enable you to describe functions, variables, macros, commands, user
options, special forms and other such artifacts in a uniform
address@hidden
+format.
In the Info file, a definition causes the entity
category---`Function', `Variable', or whatever---to appear at the
@@ -12500,7 +12499,7 @@
A manual need not and should not contain more than one definition for
a given name. An appendix containing a summary should use
address@hidden@@table} rather than the definition address@hidden
address@hidden@@table} rather than the definition commands.
@menu
* Def Cmd Template:: Writing descriptions using definition commands.
@@ -12707,11 +12706,11 @@
@var{inc} may optionally be specified as well. These arguments are
grouped with the argument @var{var} into a list, to distinguish them
from @var{body}, which includes all remaining elements of the
address@hidden
+form.
In a Texinfo source file, this @code{@@defspec} line is written like
this (except it would not be split over two lines, as it is in this
-example)address@hidden
+example).
@example
@group
@@ -12722,7 +12721,7 @@
@noindent
The function is listed in the Command and Variable Index under
address@hidden@refill
address@hidden
@node deffnx
@@ -12736,7 +12735,7 @@
the first @code{@@deffn} line by a line beginning with @code{@@deffnx}.
The @code{@@deffnx} command works exactly like @code{@@deffn}
except that it does not generate extra vertical white space between it
-and the preceding address@hidden
+and the preceding line.
@need 1000
For example,
@@ -12768,16 +12767,16 @@
@section The Definition Commands
Texinfo provides more than a dozen definition commands, all of which
-are described in this address@hidden
+are described in this section.
The definition commands automatically enter the name of the entity in
the appropriate index: for example, @code{@@deffn}, @code{@@defun},
and @code{@@defmac} enter function names in the index of functions;
@code{@@defvr} and @code{@@defvar} enter variable names in the index
-of address@hidden
+of variables.
Although the examples that follow mostly illustrate Lisp, the commands
-can be used for other programming address@hidden
+can be used for other programming languages.
@menu
* Functions Commands:: Commands for functions and similar entities.
@@ -12792,7 +12791,7 @@
@subsection Functions and Similar Entities
This section describes the commands for describing functions and similar
-entities:@refill
+entities:
@table @code
@findex deffn
@@ -12805,7 +12804,7 @@
line and is followed on the same line by the category of entity being
described, the name of this particular entity, and its arguments, if
any. Terminate the definition with @code{@@end deffn} on a line of its
address@hidden
+own.
@need 750
For example, here is a definition:
@@ -12883,7 +12882,7 @@
@subsection Variables and Similar Entities
Here are the commands for defining variables and similar
-entities:@refill
+entities:
@table @code
@findex defvr
@@ -12912,7 +12911,7 @@
@end example
Terminate the definition with @code{@@end defvr} on a line of its
address@hidden
+own.
The template is:
@@ -12930,7 +12929,7 @@
@item @@defvar @var{name}
The @code{@@defvar} command is the definition command for variables.
@code{@@defvar} is equivalent to @samp{@@defvr Variable
address@hidden@refill
address@hidden
@need 750
For example:
@@ -12954,7 +12953,7 @@
@end example
@code{@@defvar} creates an entry in the index of variables for
address@hidden@refill
address@hidden
@findex defopt
@item @@defopt @var{name}
@@ -13133,12 +13132,12 @@
something like a variable in a typed language---an entity that records
a value. You must choose a term to describe the category of the
entity being defined; for example, ``Variable'' could be used if the
-entity is a address@hidden
+entity is a variable.
The @code{@@deftypevr} command is written at the beginning of a line
and is followed on the same line by the category of the entity
being described, the data type, and the name of this particular
address@hidden
+entity.
@need 800
@noindent
@@ -13202,7 +13201,7 @@
@node Data Types
@subsection Data Types
-Here is the command for data types:@refill
+Here is the command for data types:
@table @code
@findex deftp
@@ -13215,12 +13214,12 @@
for describing @code{int} or @code{float}, in which case you could use
@code{data type} as the category. (A data type is a category of
certain objects for purposes of deciding which operations can be
-performed on them.)@refill
+performed on them.)
In Lisp, for example, @dfn{pair} names a particular data
type, and an object of that type has two slots called the
@sc{car} and the @sc{cdr}. Here is how you would write the first line
-of a definition of @address@hidden
+of a definition of @code{pair}.
@example
@group
@@ -13390,7 +13389,7 @@
For example, some systems have constructs called @dfn{wrappers} that
are associated with classes as methods are, but that act more like
macros than like functions. You could use @code{@@defop Wrapper} to
-describe one of address@hidden
+describe one of these.
Sometimes it is useful to distinguish methods and @dfn{operations}.
You can think of an operation as the specification for a method.
@@ -13400,13 +13399,13 @@
the operation has a name and also specifies the pattern of arguments;
all methods that implement the operation must accept the same
arguments, since applications that use the operation do so without
-knowing which method will implement address@hidden
+knowing which method will implement it.
Often it makes more sense to document operations than methods. For
example, window application developers need to know about the
@code{expose} operation, but need not be concerned with whether a
given class of windows has its own method to implement this operation.
-To describe this operation, you would write:@refill
+To describe this operation, you would write:
@example
@@defop Operation windows expose
@@ -13415,7 +13414,7 @@
The @code{@@defop} command is written at the beginning of a line and
is followed on the same line by the overall name of the category of
operation, the name of the class of the operation, the name of the
-operation, and its arguments, if address@hidden
+operation, and its arguments, if any.
The template is:
@example
@@ -13427,7 +13426,7 @@
@end example
@code{@@defop} creates an entry, such as address@hidden on
address@hidden', in the index of address@hidden
address@hidden', in the index of functions.
@findex deftypeop
@item @@deftypeop @var{category} @var{class} @var{data-type} @var{name}
@address@hidden
@@ -13453,7 +13452,7 @@
@code{@@defmethod} is equivalent to @samp{@@defop Method @dots{}}.
The command is written at the beginning of a line and is followed by
the name of the class of the method, the name of the method, and its
-arguments, if address@hidden
+arguments, if any.
@noindent
For example:
@@ -13495,7 +13494,7 @@
arguments that indicate the meaning, as with the @var{count} argument
to the @code{forward-word} function. Also, if the name of an argument
contains the name of a type, such as @var{integer}, take care that the
-argument actually is of that address@hidden
+argument actually is of that type.
@node Sample Function Definition
@@ -13541,7 +13540,7 @@
@end example
An interesting example of using @code{apply} is found in the description
-of @address@hidden
+of @code{mapcar}.
@end defun
@end quotation
@@ -13591,7 +13590,7 @@
@noindent
In this manual, this function is listed in the Command and Variable
-Index under @address@hidden
+Index under @code{apply}.
Ordinary variables and user options are described using a format like
that for functions except that variables do not take arguments.
@@ -15946,7 +15945,7 @@
You can switch to and from the shell buffer while @code{tex} is
running and do other editing. If you are formatting a long document
-on a slow machine, this can be very address@hidden
+on a slow machine, this can be very convenient.
You can also use @code{texi2dvi} from an Emacs shell. For example,
here is how to use @code{texi2dvi} to format and print @cite{Using and
@@ -15973,58 +15972,58 @@
formatting and printing. These include commands for sorting indices,
looking at the printer queue, killing the formatting job, and
recentering the display of the buffer in which the operations
address@hidden
+occur.
@table @kbd
@item C-c C-t C-b
@itemx M-x texinfo-tex-buffer
-Run @code{texi2dvi} on the current address@hidden
+Run @code{texi2dvi} on the current buffer.
@item C-c C-t C-r
@itemx M-x texinfo-tex-region
-Run @TeX{} on the current address@hidden
+Run @TeX{} on the current region.
@item C-c C-t C-i
@itemx M-x texinfo-texindex
Sort the indices of a Texinfo file formatted with
address@hidden@refill
address@hidden
@item C-c C-t C-p
@itemx M-x texinfo-tex-print
Print a DVI file that was made with @code{texinfo-tex-region} or
address@hidden@refill
address@hidden
@item C-c C-t C-q
@itemx M-x tex-show-print-queue
-Show the print address@hidden
+Show the print queue.
@item C-c C-t C-d
@itemx M-x texinfo-delete-from-print-queue
Delete a job from the print queue; you will be prompted for the job
number shown by a preceding @kbd{C-c C-t C-q} command
-(@code{texinfo-show-tex-print-queue})address@hidden
+(@code{texinfo-show-tex-print-queue}).
@item C-c C-t C-k
@itemx M-x tex-kill-job
Kill the currently running @TeX{} job started by either
@code{texinfo-tex-region} or @code{texinfo-tex-buffer}, or any other
-process running in the Texinfo shell address@hidden
+process running in the Texinfo shell buffer.
@item C-c C-t C-x
@itemx M-x texinfo-quit-job
Quit a @TeX{} formatting job that has stopped because of an error by
sending an @key{x} to it. When you do this, @TeX{} preserves a record
-of what it did in a @file{.log} address@hidden
+of what it did in a @file{.log} file.
@item C-c C-t C-l
@itemx M-x tex-recenter-output-buffer
Redisplay the shell buffer in which the @TeX{} printing and formatting
-commands are run to show its most recent address@hidden
+commands are run to show its most recent output.
@end table
@need 1000
Thus, the usual sequence of commands for formatting a buffer is as
-follows (with comments to the right):@refill
+follows (with comments to the right):
@example
@group
@@ -16041,11 +16040,11 @@
You can watch the commands operate in the @samp{*tex-shell*} buffer,
and you can switch to and from and use the @samp{*tex-shell*} buffer
-as you would any other shell address@hidden
+as you would any other shell buffer.
@need 1500
The formatting and print commands depend on the values of several variables.
-The default values are:@refill
+The default values are:
@example
@group
@@ -16091,7 +16090,7 @@
@kbd{M-x compile}. This creates a special shell called the
@file{*compilation*} buffer in which Emacs runs the compile command.
For example, at the end of the @file{gdb.texinfo} file, after the
address@hidden@@bye}, you could put the following:@refill
address@hidden@@bye}, you could put the following:
@example
@group
@@ -16103,7 +16102,7 @@
@noindent
This technique is most often used by programmers who also compile programs
-this way; see @ref{Compilation, , , emacs, The GNU Emacs address@hidden
+this way; see @ref{Compilation, , , emacs, The GNU Emacs Manual}.
@node Requirements Summary
@@ -16364,7 +16363,7 @@
format. However, you can direct @TeX{} to typeset a document in a 7 by
9.25 inch format that is suitable for bound books by inserting the
following command on a line by itself at the beginning of the Texinfo
-file, before the title page:@refill
+file, before the title page:
@example
@@smallbook
@@ -16379,7 +16378,7 @@
If you write the @code{@@smallbook} command between the
start-of-header and end-of-header lines, the Texinfo mode @TeX{}
region formatting command, @code{texinfo-tex-region}, will format the
-region in ``small'' book size (@pxref{Start of Header})address@hidden
+region in ``small'' book size (@pxref{Start of Header}).
@xref{small}, for information about
commands that make it easier to produce examples for a smaller manual.
@@ -16476,7 +16475,7 @@
pages with the @code{@@cropmarks} command. Write the @code{@@cropmarks}
command on a line by itself between @code{@@iftex} and @code{@@end
iftex} lines near the beginning of the Texinfo file, before the title
-page, like this:@refill
+page, like this:
@example
@group
@@ -17257,15 +17256,15 @@
@item
If a `Next', `Previous', or `Up' node reference is a reference to a
node in the current file and is not an external reference such as to
address@hidden(dir)}, then the referenced node must address@hidden
address@hidden(dir)}, then the referenced node must exist.
@item
In every node, if the `Previous' node is different from the `Up' node,
then the node pointed to by the `Previous' field must have a `Next'
-field which points back to this address@hidden
+field which points back to this node.
@item
-Every node except the `Top' node must have an `Up' address@hidden
+Every node except the `Top' node must have an `Up' pointer.
@item
The node referenced by an `Up' pointer must itself reference the current
@@ -18138,17 +18137,17 @@
You can run @code{makeinfo} in GNU Emacs Texinfo mode by using either the
@code{makeinfo-region} or the @code{makeinfo-buffer} commands. In
Texinfo mode, the commands are bound to @kbd{C-c C-m C-r} and @kbd{C-c
-C-m C-b} by address@hidden
+C-m C-b} by default.
@table @kbd
@item C-c C-m C-r
@itemx M-x makeinfo-region
-Format the current region for address@hidden
+Format the current region for Info.
@findex makeinfo-region
@item C-c C-m C-b
@itemx M-x makeinfo-buffer
-Format the current buffer for address@hidden
+Format the current buffer for Info.
@findex makeinfo-buffer
@end table
@@ -18159,7 +18158,7 @@
The Emacs @code{makeinfo-region} and @code{makeinfo-buffer} commands
run the @code{makeinfo} program in a temporary shell buffer. If
@code{makeinfo} finds any errors, Emacs displays the error messages in
-the temporary address@hidden
+the temporary buffer.
@cindex Errors, parsing
@cindex Parsing errors
@@ -18169,37 +18168,37 @@
cursor on the line in the Texinfo source that @code{makeinfo} thinks
caused the error. @xref{Compilation, , Running @code{make} or
Compilers Generally, emacs, The GNU Emacs Manual}, for more
-information about using the @code{next-error} address@hidden
+information about using the @code{next-error} command.
In addition, you can kill the shell in which the @code{makeinfo}
command is running or make the shell buffer display its most recent
address@hidden
+output.
@table @kbd
@item C-c C-m C-k
@itemx M-x makeinfo-kill-job
@findex makeinfo-kill-job
Kill the current running @code{makeinfo} job
-(from @code{makeinfo-region} or @code{makeinfo-buffer})address@hidden
+(from @code{makeinfo-region} or @code{makeinfo-buffer}).
@item C-c C-m C-l
@itemx M-x makeinfo-recenter-output-buffer
@findex makeinfo-recenter-output-buffer
Redisplay the @code{makeinfo} shell buffer to display its most recent
address@hidden
+output.
@end table
@noindent
(Note that the parallel commands for killing and recentering a @TeX{}
job are @kbd{C-c C-t C-k} and @kbd{C-c C-t C-l}. @xref{Texinfo Mode
-Printing}.)@refill
+Printing}.)
You can specify options for @code{makeinfo} by setting the
@code{makeinfo-options} variable with either the @kbd{M-x
customize} or the @kbd{M-x set-variable} command, or by setting the
variable in your @file{.emacs} initialization file.
-For example, you could write the following in your @file{.emacs} file:@refill
+For example, you could write the following in your @file{.emacs} file:
@example
@group
@@ -18239,7 +18238,7 @@
buffer and generates the Info file in it. Typing @kbd{C-x C-s} will
save the Info file under the name specified by the
@code{@@setfilename} line which must be near the beginning of the
-Texinfo address@hidden
+Texinfo file.
@table @kbd
@item C-c C-e C-r
@@ -18258,7 +18257,7 @@
provide you with further help in finding formatting errors. These
procedures are described in an appendix; see @ref{Catching Mistakes}.
However, the @code{makeinfo} program is often faster and
-provides better error checking (@pxref{makeinfo in Emacs})address@hidden
+provides better error checking (@pxref{makeinfo in Emacs}).
@node Batch Formatting
@subsection Batch Formatting
@@ -18279,17 +18278,17 @@
@noindent
Emacs processes all the files listed on the command line, even if an
-error occurs while attempting to format some of address@hidden
+error occurs while attempting to format some of them.
Run @code{batch-texinfo-format} only with Emacs in Batch mode as shown;
-it is not interactive. It kills the Batch mode Emacs on address@hidden
+it is not interactive. It kills the Batch mode Emacs on completion.
@code{batch-texinfo-format} is convenient if you lack @code{makeinfo}
and want to format several Texinfo files at once. When you use Batch
mode, you create a new Emacs process. This frees your current Emacs, so
you can continue working in it. (When you run
@code{texinfo-format-region} or @code{texinfo-format-buffer}, you cannot
-use that Emacs for anything else until the command finishes.)@refill
+use that Emacs for anything else until the command finishes.)
@node Tag and Split Files
@subsection Tag Files and Split Files
@@ -18315,20 +18314,20 @@
a way to create a single, large printed manual out of the smaller Info
files. @xref{Include Files}, for more information. Include files are
still used for very large documents, such as @cite{The Emacs Lisp
-Reference Manual}, in which each chapter is a separate file.)@refill
+Reference Manual}, in which each chapter is a separate file.)
When a file is split, Info itself makes use of a shortened version of
the original file that contains just the tag table and references to
the files that were split off. The split-off files are called
address@hidden address@hidden
address@hidden files.
The split-off files have names that are created by appending @address@hidden,
@address@hidden, @address@hidden and so on to the file name specified by the
@code{@@setfilename} command. The shortened version of the original file
-continues to have the name specified by @code{@@address@hidden
+continues to have the name specified by @code{@@setfilename}.
At one stage in writing this document, for example, the Info file was saved
-as the file @file{test-texinfo} and that file looked like this:@refill
+as the file @file{test-texinfo} and that file looked like this:
@example
@group
@@ -18361,7 +18360,7 @@
the split-off, indirect files, @file{test-texinfo-1},
@file{test-texinfo-2}, and @file{test-texinfo-3}, is listed in this file
after the line that says @samp{Indirect:}. The tag table is listed after
-the line that says @samp{Tag table:}. @refill
+the line that says @samp{Tag table:}.
In the list of indirect files, the number following the file name
records the cumulative number of bytes in the preceding indirect files,
@@ -18412,7 +18411,7 @@
The @file{dir} file is itself an Info file. It contains the top level
menu for all the Info files in the system. The menu looks like
-this:@refill
+this:
@example
@group
@@ -18431,15 +18430,15 @@
that is named in parentheses. (The menu entry does not need to
specify the `Top' node, since Info goes to the `Top' node if no node
name is mentioned. @xref{Other Info Files, , Nodes in Other Info
-Files}.)@refill
+Files}.)
Thus, the @samp{Info} entry points to the `Top' node of the
@file{info} file and the @samp{Emacs} entry points to the `Top' node
-of the @file{emacs} address@hidden
+of the @file{emacs} file.
In each of the Info files, the `Up' pointer of the `Top' node refers
back to the @code{dir} file. For example, the line for the `Top'
-node of the Emacs manual looks like this in Info:@refill
+node of the Emacs manual looks like this in Info:
@example
File: emacs Node: Top, Up: (DIR), Next: Distrib
@@ -18462,7 +18461,7 @@
To add a new Info file to your system, you must write a menu entry to
add to the menu in the @file{dir} file in the @file{info} directory.
For example, if you were adding documentation for GDB, you would write
-the following new entry:@refill
+the following new entry:
@example
* GDB: (gdb). The source-level C debugger.
@@ -21445,7 +21444,7 @@
The character @samp{@@} is used to start special Texinfo commands.
(It has the same meaning that @samp{\} has in plain @TeX{}.) Texinfo
-has four types of @@-command:@refill
+has four types of @@-command:
@table @asis
@item 1. Non-alphabetic commands.
@@ -21468,7 +21467,7 @@
These commands start with @@ followed by a letter or a word, followed by an
argument within braces. For example, the command @code{@@dfn} indicates
the introductory or defining use of a term; it is used as follows: @samp{In
-Texinfo, @@@@-commands are @@address@hidden@} address@hidden
+Texinfo, @@@@-commands are @@address@hidden@} commands.}
@item 4. Alphabetic commands that occupy an entire line.
These commands occupy an entire line. The line starts with @@,
@@ -22097,7 +22096,7 @@
Revision Control System}) or other version control systems, which
expand it into a string such as:
@example
-$Id: texinfo.txi,v 1.445 2012/06/14 18:13:51 karl Exp $
+$Id: texinfo.txi,v 1.446 2012/06/15 18:31:38 karl Exp $
@end example
(This is useful in all sources that use version control, not just manuals.)
You may wish to include the @samp{$Id:} comment in the @code{@@copying}
@@ -22403,17 +22402,17 @@
correct, but during double-sided printing, it is wise to check that
pages will bind properly---sometimes a printer will produce output in
which the even-numbered pages have a larger right-hand margin than the
-odd-numbered pages.)@refill
+odd-numbered pages.)
In the standard double-sided format, the left part of the left-hand
(even-numbered) page contains the page number, the central part is
blank, and the right part contains the title (specified by the
@code{@@settitle} command). The left part of the right-hand
(odd-numbered) page contains the name of the chapter, the central part
-is blank, and the right part contains the page address@hidden
+is blank, and the right part contains the page number.
@need 750
-Two pages, side by side as in an open book, look like this:@refill
+Two pages, side by side as in an open book, look like this:
@example
@group
@@ -22430,7 +22429,7 @@
@noindent
The chapter name is preceded by the word ``Chapter'', the chapter number
and a colon. This makes it easier to keep track of where you are in the
address@hidden
+manual.
@node Heading Choice
@section Specifying the Type of Heading
@@ -22441,32 +22440,32 @@
titlepage} command causes @TeX{} to begin to generate page headings
according to a standard format specified by the
@code{@@setchapternewpage} command that precedes the
address@hidden@@titlepage} address@hidden
address@hidden@@titlepage} section.
@need 1000
-There are four possibilities:@refill
+There are four possibilities:
@table @asis
@item No @code{@@setchapternewpage} command
Cause @TeX{} to specify the single-sided heading format, with chapters
-on new pages. This is the same as @code{@@setchapternewpage address@hidden
+on new pages. This is the same as @code{@@setchapternewpage on}.
@item @code{@@setchapternewpage on}
-Specify the single-sided heading format, with chapters on new address@hidden
+Specify the single-sided heading format, with chapters on new pages.
@item @code{@@setchapternewpage off}
Cause @TeX{} to start a new chapter on the same page as the last page of
the preceding chapter, after skipping some vertical whitespace. Also
cause @TeX{} to typeset for single-sided printing. (You can override
the headers format with the @code{@@headings double} command; see
address@hidden on off, , The @code{@@headings} Command}.)@refill
address@hidden on off, , The @code{@@headings} Command}.)
@item @code{@@setchapternewpage odd}
-Specify the double-sided heading format, with chapters on new address@hidden
+Specify the double-sided heading format, with chapters on new pages.
@end table
@noindent
-Texinfo lacks an @code{@@setchapternewpage even} address@hidden
+Texinfo lacks an @code{@@setchapternewpage even} command.
@node Custom Headings
@@ -22675,15 +22674,15 @@
and chapters.
Emacs has two tools for catching the @@-command mistakes and two for
-catching structuring address@hidden
+catching structuring mistakes.
For finding problems with @@-commands, you can run @TeX{} or a region
formatting command on the region that has a problem; indeed, you can
-run these commands on each region as you write address@hidden
+run these commands on each region as you write it.
For finding problems with the structure of nodes and chapters, you can use
@kbd{C-c C-s} (@code{texinfo-show-structure}) and the related @code{occur}
-command and you can use the @kbd{M-x Info-validate} address@hidden
+command and you can use the @kbd{M-x Info-validate} command.
@menu
* makeinfo Preferred:: @code{makeinfo} finds errors.
@@ -22720,12 +22719,12 @@
After you have written part of a Texinfo file, you can use the
@code{texinfo-format-region} or the @code{makeinfo-region} command to
-see whether the region formats address@hidden
+see whether the region formats properly.
Most likely, however, you are reading this section because for some
reason you cannot use the @code{makeinfo-region} command; therefore, the
rest of this section presumes that you are using
address@hidden@refill
address@hidden
If you have made a mistake with an @@-command,
@code{texinfo-format-region} will stop processing at or after the
@@ -22733,11 +22732,11 @@
error occurred, switch to the @samp{*Info Region*} buffer; the cursor
will be in a position that is after the location of the error. Also,
the text will not be formatted after the place where the error
-occurred (or more precisely, where it was detected)address@hidden
+occurred (or more precisely, where it was detected).
For example, if you accidentally end a menu with the command @code{@@end
menus} with an `s' on the end, instead of with @code{@@end menu}, you
-will see an error message that says:@refill
+will see an error message that says:
@example
@@end menus is not handled by texinfo
@@ -22745,7 +22744,7 @@
@noindent
The cursor will stop at the point in the buffer where the error
-occurs, or not long after it. The buffer will look like this:@refill
+occurs, or not long after it. The buffer will look like this:
@example
@group
@@ -22764,7 +22763,7 @@
@end example
The @code{texinfo-format-region} command sometimes provides slightly
-odd error messages. For example, the following cross reference fails to
format:@refill
+odd error messages. For example, the following cross reference fails to
format:
@example
(@@address@hidden Mistakes, for more info.)
@@ -22775,11 +22774,11 @@
brace but displays a message that says @samp{Unbalanced parentheses}
rather than @samp{Unbalanced braces}. This is because the formatting
command looks for mismatches between braces as if they were
address@hidden
+parentheses.
Sometimes @code{texinfo-format-region} fails to detect mistakes. For
example, in the following, the closing brace is swapped with the
-closing parenthesis:@refill
+closing parenthesis:
@example
(@@address@hidden Mistakes), for more address@hidden
@@ -22792,7 +22791,7 @@
@end example
The only way for you to detect this error is to realize that the
-reference should have looked like this:@refill
+reference should have looked like this:
@example
(*Note Catching Mistakes::, for more info.)
@@ -22820,7 +22819,7 @@
@ignore
Sometimes @code{texinfo-format-region} will stop long after the
original error; this is because it does not discover the problem until
-then. In this case, you will need to address@hidden
+then. In this case, you will need to backtrack.
@c menu
@c * Using the Emacs Lisp Debugger:: How to use the Emacs Lisp debugger.
@@ -22835,7 +22834,7 @@
If an error is especially elusive, you can turn on the Emacs Lisp
debugger and look at the backtrace; this tells you where in the
@code{texinfo-format-region} function the problem occurred. You can
-turn on the debugger with the command:@refill
+turn on the debugger with the command:
@example
M-x set-variable @key{RET} debug-on-error @key{RET} t @key{RET}
@@ -22853,17 +22852,17 @@
The byte-compiled sources send octal numbers to the debugger that may
look mysterious. To use the uncompiled source files, load
@file{texinfmt.el} and @file{texinfo.el} with the @kbd{M-x load-file}
address@hidden
+command.
The debugger will not catch an error if @code{texinfo-format-region}
does not detect one. In the example shown above,
@code{texinfo-format-region} did not find the error when the whole
list was formatted, but only when part of the list was formatted.
When @code{texinfo-format-region} did not find an error, the debugger
-did not find one either. @refill
+did not find one either.
However, when @code{texinfo-format-region} did report an error, it
-invoked the debugger. This is the backtrace it produced:@refill
+invoked the debugger. This is the backtrace it produced:
@example
---------- Buffer: *Backtrace* ----------
@@ -22893,10 +22892,10 @@
@code{texinfo-format-xref} and @code{texinfo-format-parse-args}.
Inside the function @code{texinfo-format-parse-args}, the function
@code{re-search-forward} was called; it was this function that could
-not find the missing right-hand address@hidden
+not find the missing right-hand brace.
@xref{Lisp Debug, , Debugging Emacs Lisp, emacs, The GNU Emacs
-Manual}, for more address@hidden
+Manual}, for more information.
@end ignore
@node Debugging with @TeX{}
@@ -22904,16 +22903,16 @@
@cindex Catching errors with @TeX{} formatting
@cindex Debugging with @TeX{} formatting
-You can also catch mistakes when you format a file with @address@hidden
+You can also catch mistakes when you format a file with @TeX{}.
Usually, you will want to do this after you have run
@code{texinfo-format-buffer} (or, better, @code{makeinfo-buffer}) on
the same file, because @code{texinfo-format-buffer} sometimes displays
error messages that make more sense than @TeX{}. (@xref{Debugging
-with Info}, for more information.)@refill
+with Info}, for more information.)
For example, @TeX{} was run on a Texinfo file, part of which is shown
-here:@refill
+here:
@example
---------- Buffer: texinfo.texi ----------
@@ -22927,7 +22926,7 @@
@noindent
(The cross reference lacks a closing brace.)
address@hidden produced the following output, after which it stopped:@refill
address@hidden produced the following output, after which it stopped:
@example
---------- Buffer: *tex-shell* ----------
@@ -22954,22 +22953,22 @@
@samp{@@par} is an internal @TeX{} command of no relevance to Texinfo.
@samp{l.27} means that @TeX{} detected the problem on line 27 of the
Texinfo file. The @samp{?} is the prompt @TeX{} uses in this
address@hidden
+circumstance.
Unfortunately, @TeX{} is not always so helpful, and sometimes you must
-truly be a Sherlock Holmes to discover what went address@hidden
+truly be a Sherlock Holmes to discover what went wrong.
In any case, if you run into a problem like this, you can do one of three
address@hidden
+things.
@enumerate
@item
You can tell @TeX{} to continue running and ignore just this error by
-typing @key{RET} at the @samp{?} address@hidden
+typing @key{RET} at the @samp{?} prompt.
@item
You can tell @TeX{} to continue running and to ignore all errors as best
-it can by typing @kbd{r @key{RET}} at the @samp{?} address@hidden
+it can by typing @kbd{r @key{RET}} at the @samp{?} prompt.
This is often the best thing to do. However, beware: the one error
may produce a cascade of additional error messages as its consequences
@@ -22979,7 +22978,7 @@
@item
You can tell @TeX{} to stop this run by typing @kbd{x @key{RET}}
-at the @samp{?} address@hidden
+at the @samp{?} prompt.
@end enumerate
If you are running @TeX{} inside Emacs, you need to switch to the shell
@@ -22990,7 +22989,7 @@
but @TeX{} is able to continue processing anyhow. For example, if you fail
to end an itemized list with the @code{@@end itemize} command, @TeX{} will
write a DVI file that you can print out. The only error message that
address@hidden will give you is the somewhat mysterious comment address@hidden
address@hidden will give you is the somewhat mysterious comment:
@example
(@@end occurred inside a group at level 1)
@@ -23002,17 +23001,17 @@
it were part of the last item in the itemized list. The error message
is the way @TeX{} says that it expected to find an @code{@@end}
command somewhere in the file; but that it could not determine where
-it was address@hidden
+it was needed.
Another source of notoriously hard-to-find errors is a missing
@code{@@end group} command. If you ever are stumped by
incomprehensible errors, look for a missing @code{@@end group} command
address@hidden
+first.
If the Texinfo file lacks header lines,
@TeX{} may stop in the
beginning of its run and display output that looks like the following.
-The @samp{*} indicates that @TeX{} is waiting for address@hidden
+The @samp{*} indicates that @TeX{} is waiting for input.
@example
This is TeX, Version 3.14159 (Web2c 7.0)
@@ -23025,7 +23024,7 @@
write the header lines in the Texinfo file and run the @TeX{} command
again. (Note the use of the backslash, @samp{\}. @TeX{} uses @samp{\}
instead of @samp{@@}; and in this circumstance, you are working
-directly with @TeX{}, not with Texinfo.)@refill
+directly with @TeX{}, not with Texinfo.)
@node Using texinfo-show-structure
@section Using @code{texinfo-show-structure}
@@ -23034,7 +23033,7 @@
It is not always easy to keep track of the nodes, chapters, sections, and
subsections of a Texinfo file. This is especially true if you are revising
-or adding to a Texinfo file that someone else has address@hidden
+or adding to a Texinfo file that someone else has written.
In GNU Emacs, in Texinfo mode, the @code{texinfo-show-structure}
command lists all the lines that begin with the @@-commands that
@@ -23043,11 +23042,11 @@
as prefix argument, if interactive),
the command also shows the @code{@@node} lines. The
@code{texinfo-show-structure} command is bound to @kbd{C-c C-s} in
-Texinfo mode, by address@hidden
+Texinfo mode, by default.
The lines are displayed in a buffer called the @samp{*Occur*} buffer,
indented by hierarchical level. For example, here is a part of what was
-produced by running @code{texinfo-show-structure} on this manual:@refill
+produced by running @code{texinfo-show-structure} on this manual:
@example
@group
@@ -23073,13 +23072,13 @@
@kbd{C-c C-c} command (@code{occur-mode-goto-occurrence}), to jump to
the corresponding spot in the Texinfo file. @xref{Other Repeating
Search, , Using Occur, emacs, The GNU Emacs Manual}, for more
-information about @address@hidden
+information about @code{occur-mode-goto-occurrence}.
The first line in the @samp{*Occur*} window describes the @dfn{regular
expression} specified by @var{texinfo-heading-pattern}. This regular
expression is the pattern that @code{texinfo-show-structure} looks for.
@xref{Regexps, , Using Regular Expressions, emacs, The GNU Emacs Manual},
-for more address@hidden
+for more information.
When you invoke the @code{texinfo-show-structure} command, Emacs will
display the structure of the whole buffer. If you want to see the
@@ -23087,16 +23086,16 @@
use the @kbd{C-x n n} (@code{narrow-to-region}) command to mark the
region. (@xref{Narrowing, , , emacs, The GNU Emacs Manual}.) This is
how the example used above was generated. (To see the whole buffer
-again, use @kbd{C-x n w} (@code{widen}).)@refill
+again, use @kbd{C-x n w} (@code{widen}).)
If you call @code{texinfo-show-structure} with a prefix argument by
typing @address@hidden C-c C-s}}, it will list lines beginning with
@code{@@node} as well as the lines beginning with the @@-sign commands
-for @code{@@chapter}, @code{@@section}, and the address@hidden
+for @code{@@chapter}, @code{@@section}, and the like.
You can remind yourself of the structure of a Texinfo file by looking at
the list in the @samp{*Occur*} window; and if you have mis-named a node
-or left out a section, you can correct the address@hidden
+or left out a section, you can correct the mistake.
@node Using occur
@section Using @code{occur}
@@ -23107,7 +23106,7 @@
information. Perhaps you want to remind yourself of the overall structure
of a Texinfo file, and are overwhelmed by the detailed list produced by
@code{texinfo-show-structure}. In this case, you can use the @code{occur}
-command directly. To do this, address@hidden
+command directly. To do this, type:
@example
@kbd{M-x occur}
@@ -23119,12 +23118,12 @@
emacs, The GNU Emacs Manual}.) The @code{occur} command works from
the current location of the cursor in the buffer to the end of the
buffer. If you want to run @code{occur} on the whole buffer, place
-the cursor at the beginning of the address@hidden
+the cursor at the beginning of the buffer.
For example, to see all the lines that contain the word
@samp{@@chapter} in them, just type @samp{@@chapter}. This will
produce a list of the chapters. It will also list all the sentences
-with @samp{@@chapter} in the middle of the address@hidden
+with @samp{@@chapter} in the middle of the line.
If you want to see only those lines that start with the word
@samp{@@chapter}, type @samp{^@@chapter} when prompted by
@@ -23132,10 +23131,10 @@
or phrase, end the last word with a @samp{$}; for example,
@samp{catching mistakes$}. This can be helpful when you want to see
all the nodes that are part of the same chapter or section and
-therefore have the same `Up' address@hidden
+therefore have the same `Up' pointer.
@xref{Other Repeating Search, , Using Occur, emacs , The GNU Emacs Manual},
-for more address@hidden
+for more information.
@node Running Info-Validate
@section Finding Badly Referenced Nodes
@@ -23150,14 +23149,14 @@
the `Next', `Previous', `Up' or other node pointers fail to point to a
node. This command checks that every node pointer points to an
existing node. The @code{Info-validate} command works only on Info
-files, not on Texinfo address@hidden
+files, not on Texinfo files.
The @code{makeinfo} program validates pointers automatically, so you
do not need to use the @code{Info-validate} command if you are using
@code{makeinfo}. You only may need to use @code{Info-validate} if you
are unable to run @code{makeinfo} and instead must create an Info file
using @code{texinfo-format-region} or @code{texinfo-format-buffer}, or
-if you write an Info file from address@hidden
+if you write an Info file from scratch.
@menu
* Using Info-validate:: How to run @code{Info-validate}.
@@ -23173,7 +23172,7 @@
@cindex Validating a large file
To use @code{Info-validate}, visit the Info file you wish to check and
-type:@refill
+type:
@example
M-x Info-validate
@@ -23187,10 +23186,10 @@
If your file is valid, you will receive a message that says ``File appears
valid''. However, if you have a pointer that does not point to a node,
error messages will be displayed in a buffer called @samp{*problems in
-info address@hidden
+info file*}.
For example, @code{Info-validate} was run on a test file that contained
-only the first node of this manual. One of the messages said:@refill
+only the first node of this manual. One of the messages said:
@example
In node "Overview", invalid Next: Texinfo Mode
@@ -23199,11 +23198,11 @@
@noindent
This meant that the node called @samp{Overview} had a `Next' pointer that
did not point to anything (which was true in this case, since the test file
-had only one node in it)address@hidden
+had only one node in it).
Now suppose we add a node named @samp{Texinfo Mode} to our test case
but we do not specify a `Previous' for this node. Then we will get
-the following error message:@refill
+the following error message:
@example
In node "Texinfo Mode", should have Previous: Overview
@@ -23211,10 +23210,10 @@
@noindent
This is because every `Next' pointer should be matched by a
-`Previous' (in the node where the `Next' points) which points address@hidden
+`Previous' (in the node where the `Next' points) which points back.
@code{Info-validate} also checks that all menu entries and cross references
-point to actual address@hidden
+point to actual nodes.
@code{Info-validate} requires a tag table and does not work with files
that have been split. (The @code{texinfo-format-buffer} command
@@ -23236,12 +23235,12 @@
a way that it does not create indirect subfiles. You will also need
to create a tag table for the Info file. After you have done this,
you can run @code{Info-validate} and look for badly referenced
address@hidden
+nodes.
The first step is to create an unsplit Info file. To prevent
@code{texinfo-format-buffer} from splitting a Texinfo file into
smaller Info files, give a prefix to the @kbd{M-x
-texinfo-format-buffer} command:@refill
+texinfo-format-buffer} command:
@example
C-u M-x texinfo-format-buffer
@@ -23256,7 +23255,7 @@
@noindent
When you do this, Texinfo will not split the file and will not create
-a tag table for it. @refill
+a tag table for it.
@cindex Making a tag table manually
@cindex Tag table, making manually
@@ -23264,7 +23263,7 @@
@subsection Tagifying a File
After creating an unsplit Info file, you must create a tag table for
-it. Visit the Info file you wish to tagify and type:@refill
+it. Visit the Info file you wish to tagify and type:
@example
M-x Info-tagify
@@ -23272,9 +23271,9 @@
@noindent
(Note the upper case @samp{I} in @code{Info-tagify}.) This creates an
-Info file with a tag table that you can address@hidden
+Info file with a tag table that you can validate.
-The third step is to validate the Info file:@refill
+The third step is to validate the Info file:
@example
M-x Info-validate
@@ -23282,7 +23281,7 @@
@noindent
(Note the upper case @samp{I} in @code{Info-validate}.)
-In brief, the steps are:@refill
+In brief, the steps are:
@example
@group
@@ -23295,7 +23294,7 @@
After you have validated the node structure, you can rerun
@code{texinfo-format-buffer} in the normal way so it will construct a
tag table and split the file automatically, or you can make the tag
-table and split the file address@hidden
+table and split the file manually.
@node Splitting
@subsection Splitting a File Manually
@@ -23305,12 +23304,12 @@
You should split a large file or else let the
@code{texinfo-format-buffer} or @code{makeinfo-buffer} command do it
for you automatically. (Generally you will let one of the formatting
-commands do this job for you. @xref{Creating an Info File}.)@refill
+commands do this job for you. @xref{Creating an Info File}.)
-The split-off files are called the indirect address@hidden
+The split-off files are called the indirect subfiles.
Info files are split to save memory. With smaller files, Emacs does not
-have make such a large buffer to hold the address@hidden
+have make such a large buffer to hold the information.
If an Info file has more than 30 nodes, you should also make a tag
table for it. @xref{Using Info-validate}, for information
@@ -23318,7 +23317,7 @@
automatically by the formatting command; you only need to create a tag
table yourself if you are doing the job manually. Most likely, you
will do this for a large, unsplit file on which you have run
address@hidden)@refill
address@hidden)
@c Info-split is autoloaded in `loaddefs.el' in Emacs 18.51
@ignore
@@ -23811,7 +23810,7 @@
@c shorter and the name was chosen before indenting was possible.} The
@c @code{@@refill} command is no longer important, but we describe it here
@c because you once needed it. You will see it in many old Texinfo
address@hidden address@hidden
address@hidden files.
@c
@c Without refilling, paragraphs containing long @@-constructs may look
@c bad after formatting because the formatter removes @@-commands and
@@ -23822,20 +23821,20 @@
@c end of every paragraph to cause these formatters to fill them. (Both
@c @TeX{} and @code{makeinfo} have always refilled paragraphs
@c automatically.) Now, all the Info formatters automatically fill and
address@hidden indent those paragraphs that need to be filled and address@hidden
address@hidden indent those paragraphs that need to be filled and indented.
@c
@c The @code{@@refill} command causes @code{texinfo-format-region} and
@c @code{texinfo-format-buffer} to refill a paragraph in the Info file
@c @emph{after} all the other processing has been done. For this reason,
@c you can not use @code{@@refill} with a paragraph containing either
@c @code{@@*} or @code{@@address@hidden @dots{} @}} since the refilling action
will
address@hidden override those two address@hidden
address@hidden override those two commands.
@c
@c The @code{texinfo-format-region} and @code{texinfo-format-buffer}
@c commands now automatically append @code{@@refill} to the end of each
@c paragraph that should be filled. They do not append @code{@@refill} to
@c the ends of paragraphs that contain @code{@@*} or
@address@hidden@@address@hidden @address@hidden
address@hidden and therefore do not refill or indent address@hidden
address@hidden and therefore do not refill or indent them.
@c These are no longer ``new'', and the explanations
@@ -23853,9 +23852,9 @@
@c The second edition of the Texinfo manual describes more than 20 new
@c Texinfo mode commands and more than 50 previously undocumented Texinfo
@c @@-commands. This edition is more than twice the length of the first
address@hidden address@hidden
address@hidden edition.
@c
address@hidden Here is a brief description of the new address@hidden
address@hidden Here is a brief description of the new commands.
@c
@c @c menu
@c * New Texinfo Mode Commands:: The updating commands are especially useful.
@@ -23868,9 +23867,9 @@
@c Texinfo mode provides commands and features especially designed for
@c working with Texinfo files. More than 20 new commands have been
@c added, including commands for automatically creating and updating
address@hidden both nodes and menus. This is a tedious task when done by
address@hidden
address@hidden both nodes and menus. This is a tedious task when done by hand.
@c
address@hidden The keybindings are intended to be somewhat address@hidden
address@hidden The keybindings are intended to be somewhat mnemonic.
@c
@c @c subheading Update all nodes and menus
@c
@@ -23888,7 +23887,7 @@
@c @c subheading Update Pointers
@c
@c @noindent
address@hidden Create or update `Next', `Previous', and `Up' node address@hidden
address@hidden Create or update `Next', `Previous', and `Up' node pointers.
@c
@c @noindent
@c @xref{Updating Nodes and Menus}.
@@ -23906,7 +23905,7 @@
@c @c subheading Update Menus
@c
@c @noindent
address@hidden Create or update address@hidden
address@hidden Create or update menus.
@c
@c @noindent
@c @xref{Updating Nodes and Menus}.
@@ -23929,7 +23928,7 @@
@c Insert a node's chapter or section title in the space for the
@c description in a menu entry line; position point so you can edit the
@c insert. (This command works somewhat differently than the other
address@hidden insertion commands, which insert only a predefined
string.)@refill
address@hidden insertion commands, which insert only a predefined string.)
@c
@c @noindent
@c @xref{Inserting, Inserting Frequently Used Commands}.
@@ -23944,7 +23943,7 @@
@c @noindent
@c Provide keybindings both for the Info formatting commands that are
@c written in Emacs Lisp and for @code{makeinfo} that is written in
address@hidden address@hidden
address@hidden C.
@c
@c @noindent
@c @xref{Info Formatting}.
@@ -24018,7 +24017,7 @@
@c
@c @noindent
@c The ``other updating commands'' do not have standard keybindings because
address@hidden they are used less address@hidden
address@hidden they are used less frequently.
@c
@c @noindent
@c @xref{Other Updating Commands}.
@@ -24049,12 +24048,12 @@
@c commands that were not described in the first edition. A third or so
@c of these commands existed in Texinfo but were not documented in the
@c manual; the others are new. Here is a listing, with brief
address@hidden descriptions of them:@refill
address@hidden descriptions of them:
@c
@c @c subheading Indexing
@c
@c @noindent
address@hidden Create your own index, and merge address@hidden
address@hidden Create your own index, and merge indices.
@c
@c @noindent
@c @xref{Indices}.
@@ -24075,7 +24074,7 @@
@c @noindent
@c Describe functions, variables, macros,
@c commands, user options, special forms, and other such artifacts in a
address@hidden uniform address@hidden
address@hidden uniform format.
@c
@c @noindent
@c @xref{Definition Commands}.
@@ -24094,7 +24093,7 @@
@c @noindent
@c Indicate the results of evaluation, expansion,
@c printed output, an error message, equivalence of expressions, and the
address@hidden location of address@hidden
address@hidden location of point.
@c
@c @noindent
@c @xref{Glyphs}.
@@ -24196,7 +24195,7 @@
@c Conditionally format text.
@c
@c @noindent
address@hidden @xref{set clear value, , @code{@@set} @code{@@clear}
@code{@@address@hidden
address@hidden @xref{set clear value, , @code{@@set} @code{@@clear}
@code{@@value}}.
@c
@c @table @kbd
@c @item @@set @var{flag} address@hidden
@@ -24332,7 +24331,7 @@
This is an alphabetical list of all the @@-commands, assorted Emacs Lisp
functions, and several variables. To make the list easier to use, the
-commands are listed without their preceding @samp{@@address@hidden
+commands are listed without their preceding @samp{@@}.
@printindex fn
- texinfo ChangeLog doc/texinfo.txi, Karl Berry, 2012/06/14
- texinfo ChangeLog doc/texinfo.txi,
Karl Berry <=
- texinfo ChangeLog doc/texinfo.txi, Karl Berry, 2012/06/15
- texinfo ChangeLog doc/texinfo.txi, Karl Berry, 2012/06/19
- texinfo ChangeLog doc/texinfo.txi, Karl Berry, 2012/06/20
- texinfo ChangeLog doc/texinfo.txi, Karl Berry, 2012/06/27
- texinfo ChangeLog doc/texinfo.txi, Karl Berry, 2012/06/29