all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: lxsameer <lxsameer@lxsameer.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Window focus event
Date: Fri, 17 Dec 2021 14:43:18 +0100	[thread overview]
Message-ID: <87pmpve495.fsf@web.de> (raw)
In-Reply-To: <aP2Gb1GTGygdjLpnkfZ7L3W2Bp3_QyLdlCiaRgmmoe-Jfj5aFen7Lhs5ZLGf1uidpCPKRzh0ad5LhdyujusiFB_OImP4HFg2Roen4D26AaQ=@lxsameer.com> (lxsameer@lxsameer.com's message of "Fri, 17 Dec 2021 10:28:59 +0000")

lxsameer <lxsameer@lxsameer.com> writes:

> Thanks folks, In the deprecation message of the `focus-in-hook`
> family, it refers to `after-focus-change-function`. Isn't it better to
> change that message to include these two hooks as well?

AFAIU, input focus is a per frame concept.  Window selection is
something different.  There are overlaps (the selected window is
typically in the frame that has input focus), but I don't see that
`window-configuration-change-hook' is a replacement for `focus-in-hook'
like `after-focus-change-function' is.

You can change the selected window without changing focus.  It can be
that no frame has input focus.  If a frame gets focus, that doesn't
necessarily change the window configuration, etc.  I hope my mental
model is correct.

Is there anything you could do using `focus-in-hook' that you can't do with
`after-focus-change-function'?

Michael.



  reply	other threads:[~2021-12-17 13:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 20:31 Window focus event lxsameer
2021-12-16  8:08 ` Michael Heerdegen
2021-12-16 14:30   ` Stefan Monnier
2021-12-17 10:28     ` lxsameer
2021-12-17 13:43       ` Michael Heerdegen [this message]
2021-12-17 14:28         ` lxsameer
2021-12-17 19:51       ` Stefan Kangas

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=87pmpve495.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=lxsameer@lxsameer.com \
    --cc=monnier@iro.umontreal.ca \
    /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.