all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dancol@dancol.org
To: "Daniel Colascione" <dancol@dancol.org>,
	"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: We should decouple focus and frame switching
Date: Sun, 10 Jun 2018 16:28:15 -0700	[thread overview]
Message-ID: <726a268360567d598996f0080b71c0f8.squirrel@dancol.org> (raw)
In-Reply-To: <m2a7s2cjwu.fsf@newartisans.com>

>>>>>> "DC" == Daniel Colascione <dancol@dancol.org> writes:
>
> DC> How about this? We'll add a frame-focused-p function that returns nil,
> t,
> DC> or 'unknown, and wire up focus-in-hook and focus-out-hook to run only
> when
> DC> we actually observe a window system focus change, letting the frame
> switch
> DC> stuff run completely independently. This way, we'll be able to write
> lisp
> DC> (as I've been trying to do) that reflects the real window system
> focus.
>
> DC> Sound good?
>
> Why might we not want this?

First of all, I'm worried about backward compatibility with existing
packages that rely on the current strange behavior of focus-in and
focus-out. I briefly scanned the tree, ELPA, and EmacsWiki, and I didn't
see anything that would obviously break, but that's no guarantee. The
alternative I was considering is to keep the existing focus events as they
are and add a new set of window-system-focus query functions and hooks
alongside it.

Second, Chesterton's fence: maybe there's a good reason the focus events
are structured the way they are? I was hoping somebody knew why we did it
this way in the first place.




  reply	other threads:[~2018-06-10 23:28 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 [this message]
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

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=726a268360567d598996f0080b71c0f8.squirrel@dancol.org \
    --to=dancol@dancol.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.