summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2019-12-14 13:56:29 +0200
committerEli Zaretskii <eliz@gnu.org>2019-12-14 13:56:29 +0200
commit7ebbec03eccd8d3470a6f04c87fb228e88f8f14f (patch)
treec49f4e89fa9c166f674a80df4f1c5d92cb8fd484
parent82a315b9e733deffe8802990c6312d02a576040c (diff)
downloademacs-7ebbec03eccd8d3470a6f04c87fb228e88f8f14f.tar.gz
emacs-7ebbec03eccd8d3470a6f04c87fb228e88f8f14f.tar.bz2
emacs-7ebbec03eccd8d3470a6f04c87fb228e88f8f14f.zip
Fix cross-references in ELisp manual
* doc/lispref/commands.texi (Misc Events, Special Events): Fix cross-references. (Bug#38520)
-rw-r--r--doc/lispref/commands.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 032f005e9c4..c5427b172e3 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1788,9 +1788,10 @@ additional data because signals do not carry additional information.
They can be useful for debugging (@pxref{Error Debugging}).
To catch a user signal, bind the corresponding event to an interactive
-command in the @code{special-event-map} (@pxref{Active Keymaps}).
+command in the @code{special-event-map} (@pxref{Controlling Active Maps}).
The command is called with no arguments, and the specific signal event is
-available in @code{last-input-event}. For example:
+available in @code{last-input-event} (@pxref{Event Input Misc}. For
+example:
@smallexample
(defun sigusr-handler ()
@@ -3018,7 +3019,7 @@ definition to find the actual event.
user signals like @code{sigusr1} are normally handled in this way.
The keymap which defines how to handle special events---and which
events are special---is in the variable @code{special-event-map}
-(@pxref{Active Keymaps}).
+(@pxref{Controlling Active Maps}).
@node Waiting
@section Waiting for Elapsed Time or Input