From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Should killing a help or compile buffer also delete the window?
Date: Mon, 25 Apr 2005 11:22:30 -0600 [thread overview]
Message-ID: <d4j8n2$drc$1@sea.gmane.org> (raw)
In-Reply-To: <87is2c7mnx.fsf@brockman.se>
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 that needs
> to display information in a temporary buffer. I think it just gives a
> really sloppy impression, especially when you aren't used to it.
> Two of the most common examples might be `M-x compile' and `C-h f'.
> It also happens with things like `M-x grep' and `M-x locate'.
>
> I realize that you can't expect Emacs to know when you are done with a
> window unless you actually tell when. The obvious way to tell when is
> to type `C-x 1' or `C-x 0', but this leaves the temporary buffer
> lingering, which makes me nervous.
>
> When I was new to Emacs, I would always kill a garbage buffer before
> deleting its temporary window. Eventually, I discovered `C-x 4 0' and
> started using that. As time went by (and I got lazier), I gradually
> began to accept the fact that you really can't avoid having a bunch of
> old garbage buffers unless you spend a lot of time chasing them down,
> so I started just doing `C-x 1', though it always made me feel dirty.
>
> Now to the point of this message. Some time ago I started using
> Dictionary Mode[1], which has caused me to once again pick up the
> habit of killing temporary buffers. As you might know, killing a
> dictionary buffer automatically kills the window as well, unless the
> window was already there when the dictionary buffer was created.
> This makes a lot of sense to me --- so much sense that the normal
> Emacs behavior has once again started to annoy me.
>
> I believe the Right Thing to do when the user kills a temporary buffer
> whose window was created as a side-effect of displaying the buffer in
> question is to restore the old window configuration. At least when
> the automatically created window hasn't been used for anything else,
> Emacs should take the hint and get the window out of the user's face.
Have you tried displaying those temporary buffers each in its own frame,
via special-display-buffer-names (or special-display-regexps)? That
frame's sole window is dedicated to the buffer, and so killing the
buffer deletes the frame.
--
Kevin Rodgers
next prev parent reply other threads:[~2005-04-25 17:22 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
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 [this message]
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='d4j8n2$drc$1@sea.gmane.org' \
--to=ihs_4664@yahoo.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).