From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, thuna.cing@gmail.com, emacs-devel@gnu.org
Subject: Re: Allow controlling the effect of visibility on buffer switching
Date: Sun, 30 Jan 2022 11:08:59 -0500 [thread overview]
Message-ID: <jwvtudlrz8k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <838ruxbu7u.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 30 Jan 2022 08:42:13 +0200")
>> I think this discussion would benefit from a more constructive argument
>> than habit. Can you describe use cases where `C-x b`s current default
>> is indeed the one the user wants yet it is not the last buffer (because
>> the last buffer is already visible elsewhere)?
>
> I can: when I mistakenly display (or cause Emacs to display) a buffer
> in the wrong window/frame. Then the fix is:
>
> . C-x b RET
> . go to the "correct" window/frame
> . C-x b RET
Hmm... I don't understand why you think this is an example: the first
`C-x b` will only be guaranteed to do what you intended if `C-x b`
chooses "the latest buffer" rather than "the latest buffer that's not
visible", so it seems to be an argument in favor of the proposed change.
What am I missing?
Stefan
next prev parent reply other threads:[~2022-01-30 16:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:10 Allow controlling the effect of visibility on buffer switching Thuna
2022-01-26 13:30 ` Eli Zaretskii
2022-01-26 13:46 ` Thuna
2022-01-26 15:01 ` Eli Zaretskii
2022-01-27 3:18 ` Matt Armstrong
2022-01-27 18:16 ` Thuna
2022-01-27 4:25 ` Michael Welsh Duggan
2022-01-27 17:09 ` Juri Linkov
2022-01-29 7:48 ` Thuna
2022-01-29 8:14 ` Eli Zaretskii
2022-01-29 8:35 ` Thuna
2022-01-29 9:37 ` Po Lu
2022-01-29 15:27 ` Michael Welsh Duggan
2022-01-29 20:03 ` chad
2022-01-30 7:06 ` Po Lu
2022-01-30 0:31 ` Stefan Monnier
2022-01-30 6:42 ` Eli Zaretskii
2022-01-30 16:08 ` Stefan Monnier [this message]
2022-01-30 16:51 ` Eli Zaretskii
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=jwvtudlrz8k.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=thuna.cing@gmail.com \
/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).