From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: buffer management in emacs
Date: Thu, 6 May 2010 02:52:32 -0700 (PDT) [thread overview]
Message-ID: <ddb8df24-2fab-41e4-bbfd-6c7ea9847789@e2g2000yqn.googlegroups.com> (raw)
In-Reply-To: mailman.89.1273067533.29092.help-gnu-emacs@gnu.org
On May 5, 6:51 am, Tyler Smith <tyler.sm...@eku.edu> wrote:
> Xah Lee <xah...@gmail.com> writes:
> > The emacs buffer management problem really has to do with emacs's lack
> > of closing file command. There's kill-file, but it requires you to
> > confirm, even a saved file. Plus, there's no keyboard shortcut for it.
> > So, this tends to get people to leave behind lots of opened files.
>
> Isn't 'C-x k' (kill-buffer) basically a file closing command? It doesn't
> require confirmation for files that are already saved, and the file that
> the buffer was visiting is then removed from the buffer list. Or am I
> misunderstanding what you mean by 'close file'.
>
> Also, I can't find kill-file on my emacs (GNU Emacs 24.0.50.2), did you
> mean kill-buffer to begin with?
>
> Tyler
sorry, been sloppy.
yes i meant kill-buffer (shortcut C-x k)
when you call kill-buffer, it prompts you, even for a saved file. More
specifically, it prompts you which buffer you want to kill. It does
not simply close the current buffer.
the other problem is that when you kill a buffer not asociated with a
file, even if it is not saved, has content, it'll simply kill it after
you give the buffer name, but not prompting you whether to save it.
the link i gave in my previous post does give detail about these.
Xah
∑ http://xahlee.org/
☄
next prev parent reply other threads:[~2010-05-06 9:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 21:17 buffer management in emacs .Martin.
2010-04-18 22:26 ` Claudius Hubig
2010-04-18 22:51 ` .Martin.
2010-04-19 13:35 ` Stefan Monnier
2010-04-18 22:41 ` Chris F.A. Johnson
2010-04-19 2:08 ` despen
2010-05-07 4:00 ` Kevin Rodgers
[not found] ` <mailman.35.1273204857.9285.help-gnu-emacs@gnu.org>
2010-05-07 13:58 ` despen
2010-05-08 2:35 ` Kevin Rodgers
[not found] ` <mailman.1.1273286161.603.help-gnu-emacs@gnu.org>
2010-05-08 3:00 ` despen
2010-05-08 12:29 ` Sean Sieger
[not found] ` <mailman.2.1273321768.12744.help-gnu-emacs@gnu.org>
2010-05-08 14:06 ` despen
2010-05-08 15:23 ` Sean Sieger
2010-05-08 19:17 ` Stefan Monnier
2010-05-08 21:30 ` despen
2010-05-04 8:37 ` Stefan Kamphausen
2010-05-04 13:55 ` Xah Lee
2010-05-05 13:51 ` Tyler Smith
2010-05-05 17:41 ` B. T. Raven
[not found] ` <mailman.89.1273067533.29092.help-gnu-emacs@gnu.org>
2010-05-06 9:52 ` Xah Lee [this message]
2010-05-06 9:55 ` Xah Lee
2010-05-06 15:20 ` Lennart Borgman
2010-05-06 15:34 ` Tyler Smith
2010-05-04 22:11 ` 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=ddb8df24-2fab-41e4-bbfd-6c7ea9847789@e2g2000yqn.googlegroups.com \
--to=xahlee@gmail.com \
--cc=help-gnu-emacs@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.