all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 16768@debbugs.gnu.org
Subject: bug#16768: 24.3.50; `quit-restore-window' with KILL=t replaces special-display buffer in its dedicated window
Date: Sun, 16 Feb 2014 05:33:25 +0100	[thread overview]
Message-ID: <CAAeL0SSnC4EqY2G3xAqscZfhyWCaZjvEbDYgYE20xb7eM-2cxg@mail.gmail.com> (raw)
In-Reply-To: <db85de97-2424-4f82-802e-082d2b6a2d9c@default>

On Sun, Feb 16, 2014 at 3:41 AM, Drew Adams <drew.adams@oracle.com> wrote:

> I figured someone might immediately focus on that.  It's a
> corner case.  Choose something appropriate.  Not worth
> arguing about at the outset.

It's not a corner case. Having just one frame, with one dedicated
window, and killing the buffer has happened to me, and the result
(Emacs iconifying the frame) was the wrongest of wrong choices, though
killing it would've been even worse.

> But this should be the last thing to worry about.  Debate it
> at the end if there is interest.  It should not sidetrack
> fixing the bug, taking it down a rabbit hole to never-never
> land.

Sorry, I just don't believe it's a bug. I don't think killing a frame
because a buffer was deleted and its window was dedicated is the right
thing to do. At least, as a default behavior.





  reply	other threads:[~2014-02-16  4:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 22:44 bug#16768: 24.3.50; `quit-restore-window' with KILL=t replaces special-display buffer in its dedicated window Drew Adams
2014-02-15 22:56 ` Juanma Barranquero
2014-02-16  2:41   ` Drew Adams
2014-02-16  4:33     ` Juanma Barranquero [this message]
2014-02-16  6:37       ` Drew Adams
2014-02-16 10:33 ` martin rudalics
2014-02-16 16:53   ` Drew Adams

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

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

  git send-email \
    --in-reply-to=CAAeL0SSnC4EqY2G3xAqscZfhyWCaZjvEbDYgYE20xb7eM-2cxg@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=16768@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.