From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation
Date: Wed, 21 Sep 2022 12:41:50 +0200 [thread overview]
Message-ID: <875yhh9fgx.fsf@gnus.org> (raw)
In-Reply-To: <2d1b683c2245a1b1035c@heytings.org> (Gregory Heytings's message of "Wed, 21 Sep 2022 09:14:49 +0000")
Gregory Heytings <gregory@heytings.org> writes:
>>> +This function is called with no arguments when Emacs notices that a
>>> +frame may have gotten or lost focus. Focus events are delivered
>>
>> "the focus may have moved to or from the frame." is how it usually
>> written in X documentation, and I think that is a little clearer.
Hm... I'm not sure that's clearer...
>> Also, why not add the following as well:
>>
>> when no window manager is running, or inside child frames, the focus
>> can also be set "implicitly" by the mouse pointer entering a frame.
>
> There are other cases, though, such as window managers using a
> focus-follows-mouse policy.
The original text was longer and tried to explain too much, I think --
it made it all sound very complex, scary and difficult to deal with. So
I tried to make it short and purposefully vague instead of enumerating
all different things that may and may not have happened, because that
didn't seem helpful.
next prev parent reply other threads:[~2022-09-21 10:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166368675497.15121.15081377110947098460@vcs2.savannah.gnu.org>
[not found] ` <20220920151239.61451C00871@vcs2.savannah.gnu.org>
2022-09-21 2:23 ` master 127ab231be 1/2: Attempt to clarify Input Focus documentation Po Lu
2022-09-21 9:14 ` Gregory Heytings
2022-09-21 10:41 ` Lars Ingebrigtsen [this message]
2022-09-21 10:54 ` Gregory Heytings
2022-09-21 10:51 ` Po Lu
2022-09-21 10:55 ` Lars Ingebrigtsen
2022-09-21 11:43 ` Po Lu
2022-09-21 10:58 ` Gregory Heytings
2022-09-21 11:51 ` Eli Zaretskii
2022-09-21 11:56 ` Po Lu
2022-09-21 12:53 ` Eli Zaretskii
2022-09-21 16:19 ` [External] : " Drew Adams
2022-09-21 16:36 ` Eli Zaretskii
2022-09-21 17:23 ` Drew Adams
2022-09-21 17:39 ` Eli Zaretskii
2022-09-21 21:37 ` Drew Adams
2022-09-22 2:54 ` Po Lu
2022-09-21 14:19 ` Gregory Heytings
2022-09-21 15:25 ` Andreas Schwab
2022-09-21 15:53 ` Gregory Heytings
2022-09-22 4:29 ` tomas
2022-09-22 6:53 ` Robert Pluim
2022-09-22 5:42 ` Po Lu
2022-09-21 12:07 ` Visuwesh
2022-09-21 15:06 ` tomas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yhh9fgx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=luangruo@yahoo.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).