From: martin rudalics <rudalics@gmx.at>
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 11:33:20 +0100 [thread overview]
Message-ID: <530093F0.9060409@gmx.at> (raw)
In-Reply-To: <70a2be30-e94c-44f6-8601-ce43b64bb123@default>
> This part of the `quit-restore-window' causes a special-display buffer,
> whose window is dedicated to it, to be replaced in that window by
> another buffer:
>
> (t
> ;; Show some other buffer in WINDOW and reset the quit-restore
> ;; parameter.
> (set-window-parameter window 'quit-restore nil)
> ;; Make sure that WINDOW is no more dedicated.
> (set-window-dedicated-p window nil)
> (switch-to-prev-buffer window bury-or-kill))
>
> If BURY-OR-KILL is `kill' then the window/frame should simply be
> deleted. A window dedicated to a particular buffer should not be reused
> for another buffer.
Optional second argument BURY-OR-KILL tells how to proceed with
the buffer of WINDOW.
so this is not related to whether the window or frame should be deleted.
> Consider, for example, a `special-display-frame-alist' that specifies
> certain frame attributes - e.g., a particular background color. You do
> not want to reuse such a frame for another buffer, especially for a non
> special-display buffer. The frame should be deleted when its buffer
> is killed.
IIUC a dedicated window is not deleted only if it was used before by
another buffer or it's the last window on the last frame. Can you give
a scenario with emacs -Q where such a window is not deleted?
martin
next prev parent reply other threads:[~2014-02-16 10: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
2014-02-16 6:37 ` Drew Adams
2014-02-16 10:33 ` martin rudalics [this message]
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
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=530093F0.9060409@gmx.at \
--to=rudalics@gmx.at \
--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 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).