unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: 9419-done@debbugs.gnu.org
Subject: bug#9419: 24.0.50; C-x k deletes the entire frame instead of switching to another buffer
Date: Sat, 03 Sep 2011 13:01:14 +0200	[thread overview]
Message-ID: <4E6208FA.1030404@gmx.at> (raw)
In-Reply-To: <831uw0dukq.fsf@gnu.org>

 >  emacs -Q
 >  M-x list-colors-display RET
 >  C-x 1
 >  C-x 5 b *Colors* RET
 >  C-x b foo RET
 >  C-x b *Colors* RET
 >  C-x k
 >
 > Boom! the frame is deleted, although there's at least one more buffer
 > (`foo') in that frame's nuffer list.
 >
 > This happens because window-deletable-p returns `frame' for the window
 > of the *Colors* buffer.  It does so because that buffer's window's
 > quit-restore parameter has `new-frame' as its car.  Why is that so, I
 > don't know; quit-restore doesn't seem to be documented anywhere, only
 > mentioned in a few doc strings without any explanation.  Perhaps the
 > reason is that *Colors* was the first buffer on that frame?

*Colors* was the buffer recorded in the quit-restore parameter.  I
installed a fix in revision 105644 and closed the bug.  Please check.

Thanks, martin





  reply	other threads:[~2011-09-03 11:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 17:46 bug#9419: 24.0.50; C-x k deletes the entire frame instead of switching to another buffer Eli Zaretskii
2011-09-03 11:01 ` martin rudalics [this message]
2011-09-03 11:53   ` Eli Zaretskii
2011-09-03 13:54     ` martin rudalics
2011-09-03 14:20       ` Eli Zaretskii
2011-09-03 17:29         ` martin rudalics
2011-09-03 17:44           ` Eli Zaretskii
2011-09-03 19:27             ` Eli Zaretskii
2011-09-04 10:34               ` martin rudalics
2011-09-04 16:28                 ` Eli Zaretskii
2011-09-06 13:17                   ` Stefan Monnier
2011-09-08  7:02                     ` martin rudalics
2011-09-06 13:06           ` Stefan Monnier
2011-09-08  7:02             ` martin rudalics
2011-09-08  7:02     ` martin rudalics
2011-09-09  9:16       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E6208FA.1030404@gmx.at \
    --to=rudalics@gmx.at \
    --cc=9419-done@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).