From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: lisp-complete-symbol
Date: Wed, 21 Dec 2005 19:28:21 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICMEKEDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87oe3ahxxk.fsf-monnier+emacs@gnu.org>
How 'bout the patch below instead which simply hides the *Completions*
buffer after a successful completion.
+ (let ((win (get-buffer-window "*Completions*" 0)))
+ (if win (with-selected-window win (bury-buffer)))))
"simply hides"? That depends.
Here we go again. We get into the same problems we (some of those who use
`pop-up-frames'=t) have had elsewhere - debugger, View mode, Customize,...
In each case, `bury-buffer' was added, I filed a bug report (or we discussed
it here, in the case of View mode), and `bury-buffer' was eventually
replaced with `quit-window' or something that had +/- the same effect as
`quit-window' - or by an option, letting people choose the quitting effect
they want.
Can this at least be an option? If not, if we must choose, then I vote for
`quit-window', not `bury-buffer'. I do _not_ want either 1) another buffer
taking the place of *Completions* in its (one-window) frame or 2) the
*Completions* frame flashing across my display to become an icon (the effect
iconification gives on Windows). I have no need for a *Completions*-frame
icon (who does?); I just want to delete the frame when I'm done with it -
bye bye. We've been through this discussion before. Can we please make this
work adequately for everyone?
prev parent reply other threads:[~2005-12-22 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 21:36 lisp-complete-symbol Stefan Monnier
2005-12-21 21:41 ` lisp-complete-symbol Lennart Borgman
2005-12-21 23:16 ` lisp-complete-symbol Stefan Monnier
2005-12-21 23:30 ` lisp-complete-symbol Lennart Borgman
2005-12-22 1:10 ` lisp-complete-symbol Katsumi Yamaoka
2005-12-22 1:33 ` lisp-complete-symbol Stefan Monnier
2005-12-22 3:28 ` Drew Adams [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DNEMKBNJBGPAOPIJOOICMEKEDAAA.drew.adams@oracle.com \
--to=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.