bug#25054: 25.1; bury-buffer makes bad choice of next buffer

[martin rudalics]

> My main problem is with the *mail* buffer (I have mail-user-agent set to
> 'sendmail-user-agent).  After I send mail, the *mail* buffer is buried,
> but after a while it pops up.  I would expect that, being buried, it is
> the last choice as the other buffer.  Apparently it is not.

It is.  But the "other buffer" is not necessarily the one that will be
shown in a window when that window's previous buffer is about getting
buried or killed.

> I don't know why, and I have not time to investigate now, sorry.  But if
> you care to suggest some ideas, I may find the time sooner or later :)

I suppose you mean something like

(progn
  (switch-to-buffer "a")
  (switch-to-buffer "b")
  (when (y-or-n-p "Bury b ? ")
    (bury-buffer))
  (while (y-or-n-p "Previous ? ")
    (previous-buffer)))

The loop in this scenario will eventually switch to "b" (because it has
been already shown in the selected window) rather than to "*Messages*"
(simply because it has never shown up in that window before).  We could
invent an option to change that behavior, but so far you would be its
only user.  And it's not even clear to me how to formulate that option.

martin