summaryrefslogtreecommitdiff
path: root/doc/emacs
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2018-02-21 20:32:11 +0200
committerEli Zaretskii <eliz@gnu.org>2018-02-21 20:32:11 +0200
commit106a9f60ae1d63b7d1c69950873885cdec9a2790 (patch)
tree3108b9ec6761934dcb660f75f913b3444360ba01 /doc/emacs
parent244db85d731432a739646980b2a10dba03cff409 (diff)
downloademacs-106a9f60ae1d63b7d1c69950873885cdec9a2790.tar.gz
More improvements in the Emacs manual
* doc/emacs/help.texi (Misc Help): * doc/emacs/m-x.texi (M-x): * doc/emacs/mini.texi (Minibuffer File, Repetition): Prevent breaking of command sequences between lines. Reported by Wojciech Politarczyk <w.politarczyk@gmail.com> in emacs-manual-bugs@gnu.org. * doc/emacs/sending.texi (Header Editing): Fix capitalization.
Diffstat (limited to 'doc/emacs')
-rw-r--r--doc/emacs/help.texi4
-rw-r--r--doc/emacs/m-x.texi4
-rw-r--r--doc/emacs/mini.texi4
-rw-r--r--doc/emacs/sending.texi4
4 files changed, 8 insertions, 8 deletions
diff --git a/doc/emacs/help.texi b/doc/emacs/help.texi
index 6c093f13d05..e005fe358da 100644
--- a/doc/emacs/help.texi
+++ b/doc/emacs/help.texi
@@ -595,8 +595,8 @@ typing @kbd{C-h}, @kbd{?}, or @key{F1}
few prefix keys for which not all of these keys work---those that
provide their own bindings for that key. One of these prefix keys
is @key{ESC}, because @kbd{@key{ESC} C-h} is actually @kbd{C-M-h},
-which marks a defun. However, @kbd{@key{ESC} @key{F1}} and
-@kbd{@key{ESC} ?} work fine.)
+which marks a defun. However, @w{@kbd{@key{ESC} @key{F1}}} and
+@w{@kbd{@key{ESC} ?}} work fine.)
@node Help Files
@section Help Files
diff --git a/doc/emacs/m-x.texi b/doc/emacs/m-x.texi
index a9b80d1addb..adf46ff19d7 100644
--- a/doc/emacs/m-x.texi
+++ b/doc/emacs/m-x.texi
@@ -82,8 +82,8 @@ setting of @code{suggest-key-bindings} affects these hints as well.
In this manual, when we speak of running a command by name, we often
omit the @key{RET} that terminates the name. Thus we might say
-@kbd{M-x auto-fill-mode} rather than @kbd{M-x auto-fill-mode
-@key{RET}}. We mention the @key{RET} only for emphasis, such as when
+@kbd{M-x auto-fill-mode} rather than @w{@kbd{M-x auto-fill-mode
+@key{RET}}}. We mention the @key{RET} only for emphasis, such as when
the command is followed by arguments.
@findex execute-extended-command
diff --git a/doc/emacs/mini.texi b/doc/emacs/mini.texi
index 332602dcf2a..03e371f4999 100644
--- a/doc/emacs/mini.texi
+++ b/doc/emacs/mini.texi
@@ -117,7 +117,7 @@ second slash in the pair. In the example above,
@file{/u2/emacs/src/} is ignored, so the argument you supplied is
@file{/etc/termcap}. The ignored part of the file name is dimmed if
the terminal allows it. (To disable this dimming, turn off File Name
-Shadow mode with the command @kbd{M-x file-name-shadow-mode}.)
+Shadow mode with the command @w{@kbd{M-x file-name-shadow-mode}}.)
When completing remote file names (@pxref{Remote Files}), a double
slash behaves slightly differently: it causes Emacs to ignore only the
@@ -747,7 +747,7 @@ it by typing @key{RET}.
@vindex isearch-resume-in-command-history
Incremental search does not, strictly speaking, use the minibuffer.
Therefore, although it behaves like a complex command, it normally
-does not appear in the history list for @kbd{C-x @key{ESC} @key{ESC}}.
+does not appear in the history list for @w{@kbd{C-x @key{ESC} @key{ESC}}}.
You can make incremental search commands appear in the history by
setting @code{isearch-resume-in-command-history} to a non-@code{nil}
value. @xref{Incremental Search}.
diff --git a/doc/emacs/sending.texi b/doc/emacs/sending.texi
index 491cda42177..750680b2af7 100644
--- a/doc/emacs/sending.texi
+++ b/doc/emacs/sending.texi
@@ -422,9 +422,9 @@ Move to the @samp{Cc} header (@code{message-goto-cc}).
@item C-c C-f C-b
Move to the @samp{Bcc} header (@code{message-goto-bcc}).
@item C-c C-f C-r
-Move to the @samp{Reply-To} header (@code{message-goto-reply-to}).
+Move to the @samp{Reply-to} header (@code{message-goto-reply-to}).
@item C-c C-f C-f
-Move to the @samp{Mail-Followup-To} header field
+Move to the @samp{Mail-followup-to} header field
(@code{message-goto-followup-to}).
@item C-c C-f C-w
Add a new @samp{Fcc} header field, with file-name completion