From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: 9639@debbugs.gnu.org, Stephen Berman <stephen.berman@gmx.net>
Subject: bug#9639: 24.0.90; Problem with bury-buffer in minibuffer-hide-completions
Date: Sat, 01 Oct 2011 10:41:11 -0400 [thread overview]
Message-ID: <jwvk48osrsq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4E86F22B.5060007@gmx.at> (martin rudalics's message of "Sat, 01 Oct 2011 12:57:47 +0200")
>> I confirm this DTRT for my case.
BTW, can't we just use `quit-window'?
> I believe the original idea was to mark the window as dedicated but
That's how it worked in Emacs-23, indeed.
> `display-buffer-mark-dedicated' is currently not handled by the new
> buffer display routines.
Yes, that's a bug.
> with the DEDICATED argument set. OTOH in the discussion of bug#7368 it
> was said that dedicating the completions window might harm its reuse by
> other `display-buffer' calls so I leave this to Stefan to decide what
> shall be done.
In Emacs-23, marking the window as dedicated via
display-buffer-mark-dedicated was handy but indeed had the disadvantage
of preventing the window's reuse by display-buffer. I think in Emacs-24
this disadvantage is less serious because the completion code is a lot
more careful to not leave the *Completion* displayed too long.
So making display-buffer-mark-dedicated work (which we need to do in any
case) should be all that's needed to fix the bug.
But of course, if we can get the *Completions* window/frame deleted
without marking it as dedicated, that'd be fine as well.
Stefan
next prev parent reply other threads:[~2011-10-01 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 22:09 bug#9639: 24.0.90; Problem with bury-buffer in minibuffer-hide-completions Stephen Berman
2011-10-01 9:08 ` martin rudalics
2011-10-01 10:03 ` Stephen Berman
2011-10-01 10:57 ` martin rudalics
2011-10-01 14:41 ` Stefan Monnier [this message]
2011-10-01 17:04 ` martin rudalics
2011-10-02 0:38 ` Stefan Monnier
2011-10-02 10:09 ` martin rudalics
2011-10-02 13:39 ` Stefan Monnier
2011-10-04 15:50 ` martin rudalics
2011-10-04 17:45 ` Stefan Monnier
2011-10-02 15:35 ` Drew Adams
2011-10-03 0:41 ` Stefan Monnier
2011-10-03 0:48 ` Drew Adams
2011-10-04 15:51 ` martin rudalics
2011-10-04 16:03 ` Drew Adams
2011-10-12 1:36 ` Christoph Scholtes
2011-10-12 6:52 ` martin rudalics
2011-10-04 15:51 ` martin rudalics
2011-10-01 14:38 ` Drew Adams
2011-10-01 23:38 ` Leo
2011-10-04 15:50 ` martin rudalics
2011-10-15 10:26 ` bug#5357: 23.1; Attempt to drag rightmost scrollbar martin rudalics
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=jwvk48osrsq.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9639@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=stephen.berman@gmx.net \
/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).