Subject: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer

From: Eli Zaretskii <[email-masked]>
Date: Sat, 17 Feb 2024 10:26:29 +0200

Ping! Ping! Ping!  Sam, any success in trying Martin's suggestion?

> Cc: [email-masked], [email-masked]
> Date: Sat, 10 Feb 2024 10:28:14 +0200
> From: Eli Zaretskii <[email-masked]>
> 
> Ping! Ping!  Sam, can you please try Martin's suggestion?
> 
> > Cc: [email-masked], [email-masked]
> > Date: Thu, 01 Feb 2024 11:49:50 +0200
> > From: Eli Zaretskii <[email-masked]>
> > 
> > > Date: Thu, 25 Jan 2024 10:40:07 +0100
> > > Cc: [email-masked]
> > > From: martin rudalics <[email-masked]>
> > > 
> > >  >> 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?
> > 
> > 
> > 
> > 
> 
> 
> 
>