From: Alan Mackenzie <acm@muc.de>
Subject: Re: Should killing a help or compile buffer also delete the window?
Date: Sun, 24 Apr 2005 13:35:23 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1050424122302.530A-100000@acm.acm> (raw)
In-Reply-To: <m1DPesi-0004RDC@rattlesnake.com>
On Sun, 24 Apr 2005, Robert J. Chassell wrote:
>On 24 Apr 2005, Daniel Brockman wrote,
> I've always found it annoying that Emacs seems to have a habit of
> leaving junk windows around whenever you invoke something ...
>Most often, I just want to bury the buffer, not delete it. Your two
>examples of buffers you want to delete are buffers I tend to want to
>look at again, the ones created by `M-x compile' and `C-h f'
>(describe-function).
>To me, it looks that you want `C-x 4 0' (kill-buffer-and-window) to be
>documented more prominently. What would you like specifically?
I'd like C-x 4 0 to just do its job without mithering me with "kill
buffer `foo'? (yes or no)", unless it's an actual changed buffer that's
getting killed.
>Put another way, how should we change the documentation in
>(emacs)Change Window? Right now `C-x 4 0' is third in the sequence,
>after `C-x 0' and `C-x 1'. That looks right to me.
>--
> Robert J. Chassell
--
Alan Mackenzie (Munich, Germany).
next prev parent reply other threads:[~2005-04-24 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 5:45 Should killing a help or compile buffer also delete the window? Daniel Brockman
2005-04-24 11:02 ` Robert J. Chassell
2005-04-24 13:35 ` Alan Mackenzie [this message]
2005-04-25 10:32 ` Robert J. Chassell
2005-04-24 21:22 ` Richard Stallman
2005-04-24 22:50 ` Daniel Brockman
2005-04-26 10:04 ` Richard Stallman
2005-04-25 17:20 ` Drew Adams
2005-04-25 21:38 ` Daniel Brockman
2005-04-25 17:22 ` Kevin Rodgers
2005-04-25 19:04 ` Stefan Monnier
2005-04-25 19:37 ` Daniel Brockman
2005-04-26 20:50 ` Stefan Monnier
2005-04-26 14:32 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-04-25 13:41 David Reitter
2005-04-25 14:11 ` Daniel Brockman
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=Pine.LNX.3.96.1050424122302.530A-100000@acm.acm \
--to=acm@muc.de \
/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).