From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Sun, 02 Oct 2011 12:09:45 +0200 [thread overview]
Message-ID: <4E883869.7070309@gmx.at> (raw)
In-Reply-To: <jwvwrcoqlqj.fsf-monnier+emacs@gnu.org>
>> This would delete a stand-alone frame and not iconify it.
>
> That's a problem of quit-window. I know that some users like this
> behavior, but making the distinction based on whether the code happened
> to use quit-window instead of bury-buffer is wrong, IMO.
>
> Both bury-buffer and quit-window should hide dedicated frames in the
> same way, either both by iconifying, or both by deleting the frame (and
> they should share the same code to do it).
>
> This shared code can provide a hook to let the user choose how the frame
> gets hidden, but the default should be to iconify since that's how it's
> worked until now (and also because I think it's a safer default, in the
> sense that iconifying throws away less information than deleting the
> frame).
With emacs 23 help frames are deleted by default. So if I interpret you
strictly, `quit-window' should iconify a dedicated frame and delete a
non-dedicated one. Is that correct?
Basically, it would be nice to get rid of either `bury-buffer' or
`quit-window'. Having two functions do approximately the same thing is
neither reasonable for developers nor for users.
martin
next prev parent reply other threads:[~2011-10-02 10:09 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
2011-10-01 17:04 ` martin rudalics
2011-10-02 0:38 ` Stefan Monnier
2011-10-02 10:09 ` martin rudalics [this message]
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=4E883869.7070309@gmx.at \
--to=rudalics@gmx.at \
--cc=9639@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--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).