unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: David Reitter <david.reitter@gmail.com>
Cc: 4914@debbugs.gnu.org
Subject: bug#4914: completions - remove window after use?
Date: Sun, 17 Jan 2010 18:41:11 -0500	[thread overview]
Message-ID: <87k4vg9u5k.fsf@stupidchicken.com> (raw)
In-Reply-To: <6B8057CC-08E3-4A6F-BDCC-0A8CBD738365@gmail.com>

> > When showing a *completions* buffer in a new window opened for
> > it (TAB in find-file minibuffer for instance), I wonder why the
> > window doesn't get deleted when completion has finished.  For
> > instance, when an existing file is found, the *Completions*
> > buffer is buried, but I see a split frame with the original
> > buffer in the top window and _some other_ buffer in the lower
> > window.  Shouldn't the window for the completions buffer be
> > removed whenever it has been popped up just for the buffer?
>
> I reproduce this with a current build, with emacs -nw -Q.

Do you still see this bug?  I think it's been fixed for a while now (at
least I don't experience it).






  parent reply	other threads:[~2010-01-17 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <61C01A08-8FB6-4908-B9F1-B9F1CE3E3D92@gmail.com>
     [not found] ` <4AFBC50D.1060007@gmx.at>
2009-11-12 13:31   ` bug#4914: completions - remove window after use? David Reitter
2009-11-12 17:40     ` martin rudalics
2009-11-12 17:56       ` David Reitter
2009-11-12 19:26         ` martin rudalics
2009-11-17 23:00           ` Stefan Monnier
2009-11-18  8:11             ` martin rudalics
2009-11-23 13:58             ` David Reitter
2009-11-12 20:22         ` Stefan Monnier
2010-01-17 23:41     ` Chong Yidong [this message]
     [not found]       ` <5C420BAC-187B-4B19-BF13-CC1A71745D59@gmail.com>
2010-01-18 17:58         ` David Reitter
2010-01-18 15:09     ` bug#4914: marked as done (completions - remove window after use?) Emacs bug Tracking System

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=87k4vg9u5k.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=4914@debbugs.gnu.org \
    --cc=david.reitter@gmail.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).