From: Aaron Ecay <aaronecay@gmail.com>
To: 21728@debbugs.gnu.org
Subject: bug#21728: 25.0.50; [patch] mention focus-{in,out}-hook in manual
Date: Wed, 21 Oct 2015 19:48:06 +0100 [thread overview]
Message-ID: <87lhawys61.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
The emacs lisp reference doesn’t mention focus-in-hook and its -out-
variant, except in a list of hooks. Yet it contains some discussion of
focus events. To make it clear that the hooks exist, I’ve added a
reference to them in the attached patch.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-lispref-commands.texi-Focus-Events-Mention-focus.patch --]
[-- Type: text/x-diff, Size: 894 bytes --]
From f89a1bc9d70170f77c85ca447b8a8c3efa6f1ccd Mon Sep 17 00:00:00 2001
From: Aaron Ecay <aaronecay@gmail.com>
Date: Wed, 21 Oct 2015 19:38:23 +0100
Subject: [PATCH] doc/lispref/commands.texi (Focus Events): Mention
`focus-{in,out}-hook'.
* doc/lispref/commands.texi (Focus Events): Mention `focus-{in,out}-hook'.
---
doc/lispref/commands.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 7ddf5ee..1aee2b5 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1682,6 +1682,9 @@ Focus Events
so that the focus event comes either before or after the multi-event key
sequence, and not within it.
+Another facility that Emacs provides for running lisp code on focus
+changes is @code{focus-in-hook} and @code{focus-out-hook}.
+
@node Misc Events
@subsection Miscellaneous System Events
--
2.6.1
[-- Attachment #3: Type: text/plain, Size: 67 bytes --]
(I have a copyright assignment on file.)
Thanks,
--
Aaron Ecay
next reply other threads:[~2015-10-21 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 18:48 Aaron Ecay [this message]
2015-10-21 18:57 ` bug#21728: 25.0.50; [patch] mention focus-{in,out}-hook in manual Eli Zaretskii
2016-02-23 5:31 ` Lars Ingebrigtsen
2016-02-23 15:59 ` Eli Zaretskii
2016-02-23 17:44 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhawys61.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=21728@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.