all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Aaron Maxwell <amax@redsymbol.net>, emacs-devel@gnu.org
Subject: Re: undo-kill-buffer
Date: Wed, 25 Oct 2006 09:36:19 +0900	[thread overview]
Message-ID: <87psch9qpo.fsf@catnip.gol.com> (raw)
In-Reply-To: <jwvu01t8d79.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue\, 24 Oct 2006 20\:14\:31 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Maybe it's due to a UI misfeature.  Could you explain in which context
> this happens?  Are you just using C-x k or some other way to kill the buffers?
> C-x k It's a command I almost never use.

I use C-x k a lot because I really hate having lots of buffers clutter
up the namespace -- it makes C-x C-b less useful, makes buffer-name
completion more awkward, causes newly visited file buffers to end up
with annoying suffixes (I use uniquify, so the suffixes are rational,
but I still don't like them), etc.

For whatever reason, I tend to use C-x k rather than the buffer-list "d"
command, perhaps because it's nice to have one last look at the contents
before killing.  I don't think the specific command really makes all
that much difference though; it's easy enough to accidentally kill a
buffer using buffer-list "d" too, for instance (e.g. mark a bunch of
buffers for killing and end up marking one too many without realizing
it).

[I don't tend to lose stuff though, because if there's even a slight
chance I'll find info valuable later, I put it in /tmp/,blah or something
rather than making a scratch buffer.]

-Miles
-- 
`The suburb is an obsolete and contradictory form of human settlement'

  parent reply	other threads:[~2006-10-25  0:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 15:56 undo-kill-buffer Aaron Maxwell
2006-10-24 16:11 ` undo-kill-buffer Stuart D. Herring
2006-10-24 16:46   ` undo-kill-buffer Aaron Maxwell
2006-10-24 16:36 ` undo-kill-buffer Andreas Schwab
2006-10-24 23:43 ` undo-kill-buffer Miles Bader
2006-10-24 23:51   ` undo-kill-buffer Aaron Maxwell
2006-10-25  0:14     ` undo-kill-buffer Stefan Monnier
2006-10-25  0:22       ` undo-kill-buffer Aaron Maxwell
2006-10-25  0:32         ` undo-kill-buffer Stefan Monnier
2006-10-25 14:37         ` undo-kill-buffer Stuart D. Herring
2006-10-25 16:05           ` undo-kill-buffer Drew Adams
2006-10-25 22:43           ` undo-kill-buffer Miles Bader
2006-10-25 23:02             ` undo-kill-buffer Edward O'Connor
2006-10-25 23:50               ` undo-kill-buffer Miles Bader
2006-10-26  8:53                 ` undo-kill-buffer Richard Stallman
2006-10-25 23:17             ` undo-kill-buffer David Kastrup
2006-10-25 23:46               ` undo-kill-buffer Miles Bader
2006-10-25  0:36       ` Miles Bader [this message]
2006-10-25  0:24     ` undo-kill-buffer Miles Bader
2006-10-25  1:11       ` undo-kill-buffer Aaron Maxwell
2006-10-25  0:41 ` undo-kill-buffer Drew Adams

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=87psch9qpo.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=amax@redsymbol.net \
    --cc=emacs-devel@gnu.org \
    /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.