From: dancol@dancol.org
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
Subject: Re: We should decouple focus and frame switching
Date: Sun, 10 Jun 2018 20:24:24 -0700 [thread overview]
Message-ID: <bb2db95b7516c514a6824cffad25c234.squirrel@dancol.org> (raw)
In-Reply-To: <83tvqaqcdb.fsf@gnu.org>
>> From: Daniel Colascione <dancol@dancol.org>
>> Date: Sun, 10 Jun 2018 11:07:09 -0700
>>
>> How about this? We'll add a frame-focused-p function that returns nil,
>> t, or 'unknown, and wire up focus-in-hook and focus-out-hook to run only
>> when we actually observe a window system focus change, letting the frame
>> switch stuff run completely independently. This way, we'll be able to
>> write lisp (as I've been trying to do) that reflects the real window
>> system focus.
>
> Does that mean that clicking on a frame will no longer restart cursor
> blinking when blink-cursor-mode is in its default configuration? It
> does now.
Oh, no. That'll work better than ever. Every time the focus state changes
anywhere, we'll just rescan all the frames and enable the timer if at
least one of them is a focused GUI frame, disabling otherwise. Assuming
all focus events get delivered eventually, the right thing always happens.
prev parent reply other threads:[~2018-06-11 3:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 18:07 We should decouple focus and frame switching Daniel Colascione
2018-06-10 23:16 ` John Wiegley
2018-06-10 23:28 ` dancol
2018-06-11 0:04 ` T.V Raman
2018-06-11 0:20 ` dancol
2018-06-11 1:07 ` T.V Raman
2018-06-11 13:00 ` Clément Pit-Claudel
2018-06-11 15:17 ` Stefan Monnier
2018-06-11 15:56 ` Eli Zaretskii
2018-06-13 3:34 ` Michael Heerdegen
2018-06-13 3:50 ` dancol
2018-06-11 2:35 ` Eli Zaretskii
2018-06-11 3:24 ` dancol [this message]
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=bb2db95b7516c514a6824cffad25c234.squirrel@dancol.org \
--to=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.