[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
emacs-27 1c0bc1c: Improve documentation of special events
From: |
Eli Zaretskii |
Subject: |
emacs-27 1c0bc1c: Improve documentation of special events |
Date: |
Thu, 13 Aug 2020 09:54:01 -0400 (EDT) |
branch: emacs-27
commit 1c0bc1ccd85615bcc26409ee047513e9e26f108e
Author: Eli Zaretskii <eliz@gnu.org>
Commit: Eli Zaretskii <eliz@gnu.org>
Improve documentation of special events
* doc/lispref/commands.texi (Misc Events): Explain how to bind
special events to commands.
---
doc/lispref/commands.texi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index d25f009..25f6574 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- emacs-27 1c0bc1c: Improve documentation of special events,
Eli Zaretskii <=