From: martin rudalics <rudalics@gmx.at>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: 9724@debbugs.gnu.org
Subject: bug#9724: 24.0.90; ido-mode does not kill completions buffers
Date: Thu, 13 Oct 2011 08:52:49 +0200 [thread overview]
Message-ID: <4E968AC1.1000003@gmx.at> (raw)
In-Reply-To: <4E963FE9.8050808@gmail.com>
> However, setting the variable to delete-frame still does not kill the
> *Completions* buffer on aborting the completion attempt. Am I missing
> anything?
I tried to explain that when I wrote
>>>> So, maybe this behavior is intentional. Is there any way to have the
>>>> completion buffers killed instead of buried?
>>>
>>> Sounds like bug #9639...?
>>
>> You are right. Thanks.
>
> The fix for bug#9639 doesn't change anything wrt whether the completion
> buffer gets killed or buried.
So let me try to explain this once more:
(1) Whether the buffer shall be killed or buried is decided by the
function setting up the completion buffer.
(2) Whether the window showing the completion buffer is deleted or not
is decided by (i) whether the buffer shall be killed or buried and,
if the window appears on a standalone frame and the buffer shall be
buried, (ii) the value of `frame-auto-hide-function'.
Bug#9724 is about (1) only. Bug#9639 is about (2) only and not relevant
here. Merging these two bugs was an incorrect decision.
martin
prev parent reply other threads:[~2011-10-13 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 2:27 bug#9724: 24.0.90; ido-mode does not kill completions buffers Christoph Scholtes
2011-10-11 3:36 ` Christoph Scholtes
2011-10-11 4:55 ` Drew Adams
2011-10-12 1:45 ` Christoph Scholtes
2011-10-12 6:52 ` martin rudalics
2011-10-12 12:28 ` Christoph Scholtes
2011-10-12 14:25 ` martin rudalics
2011-10-13 1:33 ` Christoph Scholtes
2011-10-13 6:52 ` martin rudalics [this message]
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=4E968AC1.1000003@gmx.at \
--to=rudalics@gmx.at \
--cc=9724@debbugs.gnu.org \
--cc=cschol2112@googlemail.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).