aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2001-04-18 18:44:01 +0000
committerEli Zaretskii2001-04-18 18:44:01 +0000
commit79c43dcd9665be8ed0cbb3f2f5e97762982f1c25 (patch)
treed8df15e923ac6800217cca08231e06c2d2a2faea
parent0f8d6dc7c26f0cd03a159b5271936d347e2f900b (diff)
downloademacs-79c43dcd9665be8ed0cbb3f2f5e97762982f1c25.tar.gz
emacs-79c43dcd9665be8ed0cbb3f2f5e97762982f1c25.zip
Fix markup of control characters.
-rw-r--r--man/info.texi27
1 files changed, 14 insertions, 13 deletions
diff --git a/man/info.texi b/man/info.texi
index 2c74d7d979b..b5542d435a4 100644
--- a/man/info.texi
+++ b/man/info.texi
@@ -6,7 +6,7 @@
6@syncodeindex vr cp 6@syncodeindex vr cp
7@syncodeindex ky cp 7@syncodeindex ky cp
8@comment %**end of header 8@comment %**end of header
9@comment $Id: info.texi,v 1.10 2001/04/15 08:43:53 eliz Exp $ 9@comment $Id: info.texi,v 1.11 2001/04/17 12:13:47 eliz Exp $
10 10
11@dircategory Texinfo documentation system 11@dircategory Texinfo documentation system
12@direntry 12@direntry
@@ -404,7 +404,7 @@ In that case, @kbd{b} won't do anything. Sorry; what can we do?
404@findex Info-summary 404@findex Info-summary
405 You have just learned a considerable number of commands. If you 405 You have just learned a considerable number of commands. If you
406want to use one but have trouble remembering which, you should type 406want to use one but have trouble remembering which, you should type
407a @key{?} (in Emacs it runs the @code{Info-summary} command) which 407a @kbd{?} (in Emacs it runs the @code{Info-summary} command) which
408prints out a brief list of commands. When you are finished looking at 408prints out a brief list of commands. When you are finished looking at
409the list, make it go away by typing a @key{SPC} repeatedly. 409the list, make it go away by typing a @key{SPC} repeatedly.
410 410
@@ -1013,16 +1013,17 @@ them. However, if you want to edit an Info file, here is how.
1013 1013
1014@cindex node delimiters 1014@cindex node delimiters
1015 The new node can live in an existing documentation file, or in a new 1015 The new node can live in an existing documentation file, or in a new
1016one. It must have a @key{^_} character before it (invisible to the 1016one. It must have a @samp{^_} character before it (invisible to the
1017user; this node has one but you cannot see it), and it ends with either 1017user; this node has one but you cannot see it), and it ends with either
1018a @key{^_}, a @key{^L}, or the end of file.@footnote{If you put in a 1018a @samp{^_}, a @samp{^L} (``formfeed''), or the end of file.@footnote{If
1019@key{^L} to end a new node, be sure that there is a @key{^_} after it 1019you put in a @samp{^L} to end a new node, be sure that there is a
1020to start the next one, since @key{^L} cannot @emph{start} a node. 1020@samp{^_} after it to start the next one, since @samp{^L} cannot
1021Also, a nicer way to make a node boundary be a page boundary as well 1021@emph{start} a node. Also, a nicer way to make a node boundary be a
1022is to put a @key{^L} @emph{right after} the @key{^_}.} 1022page boundary as well is to put a @samp{^L} @emph{right after} the
1023 1023@samp{^_}.}
1024 The @key{^_} starting a node must be followed by a newline or a 1024
1025@key{^L} newline, after which comes the node's header line. The header 1025 The @samp{^_} starting a node must be followed by a newline or a
1026@samp{^L} newline, after which comes the node's header line. The header
1026line must give the node's name (by which Info finds it), and state the 1027line must give the node's name (by which Info finds it), and state the
1027names of the @samp{Next}, @samp{Previous}, and @samp{Up} nodes (if there 1028names of the @samp{Next}, @samp{Previous}, and @samp{Up} nodes (if there
1028are any). As you can see, this node's @samp{Up} node is the node 1029are any). As you can see, this node's @samp{Up} node is the node
@@ -1191,7 +1192,7 @@ End Tag Table
1191@noindent 1192@noindent
1192Note that it contains one line per node, and this line contains 1193Note that it contains one line per node, and this line contains
1193the beginning of the node's header (ending just after the node name), 1194the beginning of the node's header (ending just after the node name),
1194a @key{DEL} character, and the character position in the file of the 1195a @samp{DEL} character, and the character position in the file of the
1195beginning of the node. 1196beginning of the node.
1196 1197
1197 1198
@@ -1267,7 +1268,7 @@ hit the end of the current node. The default is @code{t}.
1267When set to a non-@code{nil} value, allows Info to execute Lisp code 1268When set to a non-@code{nil} value, allows Info to execute Lisp code
1268associated with nodes. The Lisp code is executed when the node is 1269associated with nodes. The Lisp code is executed when the node is
1269selected. The Lisp code to be executed should follow the node 1270selected. The Lisp code to be executed should follow the node
1270delimiter (the @key{DEL} character) and an @samp{execute: } tag, like 1271delimiter (the @samp{DEL} character) and an @samp{execute: } tag, like
1271this: 1272this:
1272 1273
1273@example 1274@example