procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix recent Command Modes changes in Elisp manual

Browse source 
* doc/lispref/commands.texi (Command Modes): Fix typos and grammar.
Cross-reference the 'declare' form node.
This commit is contained in:
Basil L. Contovounesios 2021-02-17 22:49:15 +00:00
parent 6d0089cabc
commit a68a5fe03a
1 changed files with 8 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/lispref/commands.texi
View file

@ -603,10 +603,11 @@ mode that has editable text, and commands that display information
Many other commands, however, are specifically tied to a mode, and
make no sense outside of that context. For instance, @code{M-x
dired-diff} will just signal an error used outside of a dired buffer.
dired-diff} will just signal an error if used outside of a Dired
buffer.
Emacs therefore has a mechanism for specifying what mode (or modes) a
command ``belong'' to:
command ``belongs'' to:
@lisp
(defun dired-diff (...)
@ -634,8 +635,8 @@ commands (if they aren't bound to any keys).
If using this extended @code{interactive} form isn't convenient
(because the code is supposed to work in older versions of Emacs that
doesn't support the extended @code{interactive} form), the following
can be used instead:
don't support the extended @code{interactive} form), the following
equivalent declaration (@pxref{Declare Form}) can be used instead:
@lisp
(declare (modes dired-mode))
@ -657,10 +658,10 @@ call @code{kill-buffer}. This command will ``work'' from any mode,
but it is highly unlikely that anybody would actually want to use the
command outside the context of this special mode.
Many modes have a set of different commands that start that start the
mode in different ways, (e.g., @code{eww-open-in-new-buffer} and
Many modes have a set of different commands that start the mode in
different ways (e.g., @code{eww-open-in-new-buffer} and
@code{eww-open-file}). Commands like that should never be tagged as
mode-specific, as then can be issued by the user from pretty much any
mode-specific, as they can be issued by the user from pretty much any
context.
@node Generic Commands