From: Kim F. Storm <storm@cua.dk>
Date: Mon, 4 Dec 2006 12:30:20 +0000 (+0000)
Subject: (Misc Events): Update signal events.
X-Git-Tag: emacs-pretest-22.0.92~314
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=d96658e3fd1586182c54ded540401a3bd00e6465;p=emacs.git

(Misc Events): Update signal events.
(Event Examples): Add signal example.
---

diff --git a/lispref/commands.texi b/lispref/commands.texi
index 124be554b63..7188961e344 100644
--- a/lispref/commands.texi
+++ b/lispref/commands.texi
@@ -1586,13 +1586,14 @@ The precise meaning of the event parameters and the way these
 parameters are used to display the help-echo text are described in
 @ref{Text help-echo}.
 
-@cindex @code{usr1-signal} event
-@cindex @code{usr2-signal} event
-@item usr1-signal
-@itemx usr2-signal
-These events are generated when the Emacs process receives the signals
-@code{SIGUSR1} and @code{SIGUSR2}.  They contain no additional data
-because signals do not carry additional information.
+@cindex @code{signal usr1} event
+@cindex @code{signal usr2} event
+@cindex user signals
+@item signal usr1
+@itemx signal usr2
+These event sequences are generated when the Emacs process receives
+the signals @code{SIGUSR1} and @code{SIGUSR2}.  They contain no
+additional data because signals do not carry additional information.
 @end table
 
   If one of these events arrives in the middle of a key sequence---that
@@ -1632,6 +1633,16 @@ into another window.  That produces a pair of events like these:
                    -453816))
 @end smallexample
 
+To handle a SIGUSR1 signal, define an interactive function, and
+bind it to the @code{signal usr1} event sequence:
+
+@smallexample
+(defun usr1-handler ()
+  (interactive)
+  (message "Got USR1 signal"))
+(global-set-key [signal usr1] 'usr1-handler)
+@end smallexample
+
 @node Classifying Events
 @subsection Classifying Events
 @cindex event type