summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2020-08-13 16:53:14 +0300
committerEli Zaretskii <eliz@gnu.org>2020-08-13 16:53:14 +0300
commit1c0bc1ccd85615bcc26409ee047513e9e26f108e (patch)
treef8658fbf13e4cb6afe01f0c0e71fdc0c47ded818 /doc
parentc9a739408d286b52782c9005dcac97304c13d273 (diff)
downloademacs-1c0bc1ccd85615bcc26409ee047513e9e26f108e.tar.gz
Improve documentation of special events
* doc/lispref/commands.texi (Misc Events): Explain how to bind special events to commands.
Diffstat (limited to 'doc')
-rw-r--r--doc/lispref/commands.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index d25f0093618..25f657404f3 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1845,6 +1845,13 @@ is, after a prefix key---then Emacs reorders the events so that this
event comes either before or after the multi-event key sequence, not
within it.
+ Some of these special events, such as @code{delete-frame}, invoke
+Emacs commands by default; others are not bound. If you want to
+arrange for a special event to invoke a command, you can do that via
+@code{special-event-map}. The command you bind to a function key in
+that map can then examine the full event which invoked it in
+@code{last-input-event}. @xref{Special Events}.
+
@node Event Examples
@subsection Event Examples