From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tyler Smith Newsgroups: gmane.emacs.help Subject: Re: buffer management in emacs Date: Thu, 06 May 2010 11:34:02 -0400 Message-ID: <87d3x9jb85.fsf@eku238261.eku.edu> References: <87d3xwsbns.fsf@slack64.serverdot.org> <276ba00e-2f6e-4e66-ac82-f1b69f0a0587@u20g2000pru.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1273166102 5846 80.91.229.12 (6 May 2010 17:15:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 6 May 2010 17:15:02 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu May 06 19:15:00 2010 connect(): No such file or directory Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OA4f3-0000Ox-Sk for geh-help-gnu-emacs@m.gmane.org; Thu, 06 May 2010 19:14:58 +0200 Original-Received: from localhost ([127.0.0.1]:48111 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OA4f3-0004Yd-3e for geh-help-gnu-emacs@m.gmane.org; Thu, 06 May 2010 13:14:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1OA361-0000bS-PJ for help-gnu-emacs@gnu.org; Thu, 06 May 2010 11:34:42 -0400 Original-Received: from [140.186.70.92] (port=45475 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OA35x-0000XF-6U for help-gnu-emacs@gnu.org; Thu, 06 May 2010 11:34:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OA35s-0005SS-AG for help-gnu-emacs@gnu.org; Thu, 06 May 2010 11:34:37 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:40925) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OA35r-0005Rh-Uo for help-gnu-emacs@gnu.org; Thu, 06 May 2010 11:34:32 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OA35n-0004HT-NX for help-gnu-emacs@gnu.org; Thu, 06 May 2010 17:34:27 +0200 Original-Received: from 157.89.133.36 ([157.89.133.36]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 May 2010 17:34:27 +0200 Original-Received: from tyler.smith by 157.89.133.36 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 May 2010 17:34:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ connect(): No such file or directory Original-Lines: 37 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 157.89.133.36 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:EEig5A+6oM1uWlX4QpxxERwAnAM= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:73514 Archived-At: Xah Lee writes: > On May 5, 6:51 am, Tyler Smith wrote: >> Xah Lee 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. Ah! I understand now. It does actually ask for confirmation of which buffer you want to kill, but if you just hit return, the default is to close the current buffer. So the sequence 'C-x k ' will kill the current buffer. I don't even notice that I'm pressing anymore, since I never use this function to kill buffers other than the current one. Cheers, Tyler