From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: erase-buffer (was: with-output-to-temp-buffer) Date: Tue, 11 May 2004 19:26:51 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040511232651.GB5298@fencepost> References: <200405020157.KAA07108@etlken.m17n.org> <200405060505.OAA21188@etlken.m17n.org> <200405061310.WAA22378@etlken.m17n.org> <200405101213.VAA04125@etlken.m17n.org> <87ekpsuzqa.fsf-monnier+emacs@gnu.org> <877jvjnl4g.fsf-monnier+emacs@gnu.org> <200405112306.IAA09060@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084318460 1326 80.91.224.253 (11 May 2004 23:34:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 23:34:20 +0000 (UTC) Cc: juri@jurta.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed May 12 01:34:10 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNglF-00034F-00 for ; Wed, 12 May 2004 01:34:09 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNglE-0008BM-00 for ; Wed, 12 May 2004 01:34:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNggT-0003mM-8h for emacs-devel@quimby.gnus.org; Tue, 11 May 2004 19:29:13 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNgeq-0003HN-Bq for emacs-devel@gnu.org; Tue, 11 May 2004 19:27:32 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNgeI-0003Cf-Is for emacs-devel@gnu.org; Tue, 11 May 2004 19:27:29 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNgeI-0003Cb-4G for emacs-devel@gnu.org; Tue, 11 May 2004 19:26:58 -0400 Original-Received: from miles by fencepost.gnu.org with local (Exim 4.34) id 1BNgeB-0002Of-MX; Tue, 11 May 2004 19:26:51 -0400 Original-To: Kenichi Handa Content-Disposition: inline In-Reply-To: <200405112306.IAA09060@etlken.m17n.org> User-Agent: Mutt/1.3.28i Blat: Foop X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23193 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23193 On Wed, May 12, 2004 at 08:06:21AM +0900, Kenichi Handa wrote: > > So my question is: why is erase-buffer a command? > > I didn't know it was a command until 5 days ago, it is not bound to any > > key, and I can't think of any circumstance where a user might want to say > > M-x erase-buffer RET. > > I often use it in *shell* and *gdb* buffers when they grow > too much. It's a `weird' command in the way it ignores normal restrictions though. I think for user-use, it might make more sense to define some other command that acts more normally (i.e., obeys buffer narrowing, etc.). Perhaps call it `delete-whole-buffer' (analogous to `mark-whole-buffer'). [Are there in fact programmatic uses that depend on erase-buffer's weird behavior? I'll bet in some cases, it might actually be a bug...] -Miles -- "I distrust a research person who is always obviously busy on a task." --Robert Frosch, VP, GM Research