From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Cardaci <cyrus.and@gmail.com>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Zoom: a window management minor mode -- best practices and questions
Date: Tue, 08 May 2018 20:52:46 +0300 [thread overview]
Message-ID: <83muxaox01.fsf@gnu.org> (raw)
In-Reply-To: <CACMsj9M5-oar40u+NgvY3to2t-Y3aTLhidcTt2LVCSnY6TkSmQ@mail.gmail.com> (message from Andrea Cardaci on Tue, 8 May 2018 12:40:01 +0200)
> From: Andrea Cardaci <cyrus.and@gmail.com>
> Date: Tue, 8 May 2018 12:40:01 +0200
> Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
>
> > I don't remember (perhaps Martin does). But if you show a C-level
> > backtrace from such a call to buffer-list-update-hook, it will be easy
> > to say whether this is expected or not.
>
> Is there a simple way to dump a backtrace from Emacs?
>
> It's easy to reproduce tough:
>
> (defun foo ()
> (message "buffer-list-update-hook"))
>
> (add-hook 'buffer-list-update-hook 'foo)
>
> then simply click in the selected window.
>
> Anyway according to the documentation this hook is called by
> `select-window` which is actually called if you click on a window,
> even if it is the selected one.
Yes, and the comments in select-window say that it's important it
moves the selected window's buffer to the front of various alists,
which is done by record_buffer. So I guess this is a feature. Maybe
we could be smarter, and avoid calling the hook if the buffer is
already at the front of those alists.
next prev parent reply other threads:[~2018-05-08 17:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 16:31 Zoom: a window management minor mode -- best practices and questions Andrea Cardaci
2018-05-02 17:32 ` Eli Zaretskii
2018-05-02 18:41 ` Andrea Cardaci
2018-05-02 18:58 ` Eli Zaretskii
2018-05-03 7:11 ` martin rudalics
2018-05-03 9:50 ` Andrea Cardaci
2018-05-03 9:46 ` Andrea Cardaci
2018-05-03 7:11 ` martin rudalics
2018-05-03 9:47 ` Andrea Cardaci
2018-05-07 12:32 ` Andrea Cardaci
2018-05-07 18:19 ` Eli Zaretskii
2018-05-08 10:40 ` Andrea Cardaci
2018-05-08 14:53 ` Noam Postavsky
2018-05-08 15:03 ` Andrea Cardaci
2018-05-09 12:33 ` Stefan Monnier
2018-05-08 17:52 ` Eli Zaretskii [this message]
2018-05-09 7:00 ` martin rudalics
2018-05-09 16:06 ` Andrea Cardaci
2018-05-10 6:27 ` martin rudalics
2018-05-10 10:11 ` Andrea Cardaci
2018-05-10 10:27 ` martin rudalics
2018-05-10 10:34 ` Andrea Cardaci
2018-05-10 10:37 ` 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=83muxaox01.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyrus.and@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).