Re: improving function "mode-line-unbury-buffer" in bindings.el

[storm@cua.dk (Kim F. Storm)]

Richard Stallman <rms@gnu.org> writes:

>     Here is what is CLAIMED to happen with bury-buffer:
> 
>     When you use bury-buffer to bury the buffer in the selected window,
>     the NEXT buffer to be shown in the selected window is chosen with a
>     preference to show a buffer which has previously been shown in a
>     window.
> 
> What I see in the code of Fother_buffer is that it prefers the buffers
> that have been shown in this frame before.  However, burying a buffer
> removes it from the frame's buffer list (this is a recent bug fix).
> So as you cycle in this way, the frame's buffer list will empty out
> and you will indeed get all the non-hidden buffers.
> 
>     - doing bury-buffer once will bury xyz and show *scratch*, and
>     - doing bury-buffer again will bury *scratch* and show xyz.
> 
> I get *Messages* the third time now.

So do I (which is why I said "CLAIMED to happen" in my explanation).

So with the recent change to bury-buffer, unbury-buffer now does the
right thing I guess.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk