From: dalanicolai <dalanicolai@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 54438@debbugs.gnu.org
Subject: bug#54438: 27.2; inconsistent-behavior-global-vs-local-hook
Date: Fri, 18 Mar 2022 18:03:22 +0100 [thread overview]
Message-ID: <CACJP=3=d4zbDw447Lf7mYdd4Cmt1QVrP5LXTvae5gWV_KBrvtA@mail.gmail.com> (raw)
In-Reply-To: <jwvr16z31dq.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Thanks for your explanations... (although I will need some time to think
about and understand them)
On Fri, 18 Mar 2022 at 13:14, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> >> Also, I would expect that a hook just calls the hook function, and it
> would
> >> not 'restore the window
> >> selected before the hook'. I would say the restoring is undesired
> behavior.
> >
> > The idea is probably that a function on that hook should be allowed to
> > inadvertently select some other window and have the hook runner fix
> > that. Maybe Stefan can tell us more.
>
> No, IIRC it is just a consequence of needing to select windows when
> running the local part of the hook (since that part is supposed to be
> run for every window (which was modified) displaying that buffer).
>
>
> Stefan
>
>
[-- Attachment #2: Type: text/html, Size: 1185 bytes --]
next prev parent reply other threads:[~2022-03-18 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 17:52 bug#54438: 27.2; inconsistent-behavior-global-vs-local-hook dalanicolai
2022-03-18 0:42 ` Michael Heerdegen
2022-03-18 8:37 ` martin rudalics
2022-03-18 9:11 ` dalanicolai
2022-03-18 9:12 ` dalanicolai
2022-03-18 9:58 ` martin rudalics
2022-03-18 12:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-18 17:03 ` dalanicolai [this message]
2022-03-18 8:36 ` martin rudalics
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='CACJP=3=d4zbDw447Lf7mYdd4Cmt1QVrP5LXTvae5gWV_KBrvtA@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--cc=54438@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--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 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).