bug#9419: 24.0.50; C-x k deletes the entire frame instead of switching to another buffer

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 03 Sep 2011 13:01:14 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: Eli Zaretskii <eliz@gnu.org>
> 
> *Colors* was the buffer recorded in the quit-restore parameter.  I
> installed a fix in revision 105644 and closed the bug.  Please check.

Thanks.

The original use case seems to work now, i.e. the frame is not
deleted.  The following also works, IIUC the intent:

  emacs -Q
  C-x 5 b foo RET
  C-x k RET

This kills buffer foo and deletes the second frame.  Is this the
intended behavior?

However, this use case looks inconsistent, or maybe I don't understand
the intended behavior:

  emacs -Q
  C-x 5 b foo RET

then in the new frame:

  C-x b bar RET
  C-x b foo RET
  C-x k RET      (kills the foo buffer and shows bar)
  C-x k RET      (kills the bar buffer and shows *scratch*)

My understanding of the intended behavior is that since foo and bar
are the only 2 buffers in that frame's buffer list, the frame should
be deleted after the last one of them is deleted.  But in fact the
frame stays alive and shows *scratch*.

If I kill the buffers in the reverse order, i.e. bar first and then
foo, the frame does get deleted when foo is killed.