From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 67993@debbugs.gnu.org
Subject: bug#67993: Selecting buffer automatically
Date: Wed, 10 Jan 2024 19:12:50 +0200 [thread overview]
Message-ID: <867ckhqgqp.fsf@mail.linkov.net> (raw)
In-Reply-To: <942ced7b-53f8-4b33-9280-6cdba4b6ed6b@gmx.at> (martin rudalics's message of "Wed, 10 Jan 2024 09:37:26 +0100")
>>> That's why any such 'select-window' call (or its avoidance) you
>>> propose would be better handled within 'display-buffer' and not later
>>> in a 'post-command-hook'.
>>
>> No way to call 'select-window' immediately, because this will
>> break too many functions that expect a window to be selected
>> from the previous call of pop-to-buffer until the command
>> is finished.
>
> Do you mean that if I have two 'pop-to-buffer' calls within one and the
> same command, the first one has a (select-window . nil) entry and the
> second one no such entry, then the entry from the first call will cause
> the window from the second call to get deselected? If so, then this
> deserves a special explanation in the manual.
This is what I see with the current patch:
1.
(let ((display-buffer-alist '(("1" nil (select-window . nil)))))
(delete-other-windows) (split-window) (split-window) (balance-windows)
(pop-to-buffer (get-buffer-create "1"))
(pop-to-buffer (get-buffer-create "2")))
then the original window remains selected.
2.
(let ((display-buffer-alist '(("2" nil (select-window . nil)))))
(delete-other-windows) (split-window) (split-window) (balance-windows)
(pop-to-buffer (get-buffer-create "1"))
(pop-to-buffer (get-buffer-create "2")))
then the window with "1" is selected after the command finishes.
next prev parent reply other threads:[~2024-01-10 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 17:51 bug#67993: Selecting buffer automatically Juri Linkov
2024-01-04 17:12 ` Juri Linkov
2024-01-05 9:23 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-06 17:40 ` Juri Linkov
2024-01-07 14:56 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-07 16:51 ` Juri Linkov
2024-01-08 8:55 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-09 17:20 ` Juri Linkov
2024-01-10 8:37 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 17:12 ` Juri Linkov [this message]
2024-01-11 9:15 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 7:46 ` Juri Linkov
2024-01-13 10:39 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 18:48 ` Juri Linkov
2024-01-15 10:23 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 17:56 ` Juri Linkov
2024-01-16 10:18 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 16:54 ` Juri Linkov
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=867ckhqgqp.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=67993@debbugs.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).