From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 68679@debbugs.gnu.org, sds@gnu.org
Subject: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer
Date: Thu, 01 Feb 2024 11:49:50 +0200 [thread overview]
Message-ID: <867cjo1pkx.fsf@gnu.org> (raw)
In-Reply-To: <73f77d65-9cb4-4d09-a80f-56aed7055732@gmx.at> (message from martin rudalics on Thu, 25 Jan 2024 10:40:07 +0100)
> Date: Thu, 25 Jan 2024 10:40:07 +0100
> Cc: 68679@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> >> ISTR that quit-window and bury-buffer made sure that the
> >> replacement/newly displayed buffer is not shown in any other window (at
> >> least that was my intention when I wrote quit-window many years ago).
> >>
> >> Right now I see that C-x b (switch-to-buffer) offers a good candidate
> >> (IOW, other-buffer returns a buffer that is not currently shown), but
> >> both quit-window and bury-buffer replace the current buffer with one
> >> that is already displayed in another window in the current frame.
>
> More precisely "may replace".
>
> >> Is there a way to restore the original behavior of never displaying an
> >> already visible buffer?
> >>
> >> Is this a (known) bug?
>
> Can you try customizing 'switch-to-prev-buffer-skip'?
Ping! Sam, can you try Martin's suggestion and tell if it solves your
problem?
next prev parent reply other threads:[~2024-02-01 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 0:11 bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer Sam Steingold
2024-01-24 12:28 ` Eli Zaretskii
2024-01-25 9:40 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 9:49 ` Eli Zaretskii [this message]
2024-02-10 8:28 ` Eli Zaretskii
2024-02-17 8:26 ` 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=867cjo1pkx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68679@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=sds@gnu.org \
/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).