GNU bug report logs - #68679
30.0.50; Burying a buffer shows an already displayed buffer

Previous Next

Full log

Message #14 received at 68679 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 68679 <at> debbugs.gnu.org, sds <at> gnu.org
Subject: Re: bug#68679: 30.0.50; Burying a buffer shows an already displayed
 buffer
Date: Thu, 01 Feb 2024 11:49:50 +0200

> Date: Thu, 25 Jan 2024 10:40:07 +0100
> Cc: 68679 <at> debbugs.gnu.org
> From: martin rudalics <rudalics <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.