From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.help Subject: Re: How to get rid of *GNU Emacs* buffer on start-up? Date: Sat, 20 Sep 2008 08:50:00 +0000 Message-ID: <20080920085000.GB1685@muc.de> References: <873ajzwoqu.fsf@kobe.laptop> <823901dd-c54c-4e3b-b6ad-512d52724a46@z11g2000prl.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1221900273 14689 80.91.229.12 (20 Sep 2008 08:44:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 20 Sep 2008 08:44:33 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Xah Lee Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Sep 20 10:45:29 2008 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.50) id 1Kgy5p-0004vI-4A for geh-help-gnu-emacs@m.gmane.org; Sat, 20 Sep 2008 10:45:29 +0200 Original-Received: from localhost ([127.0.0.1]:43188 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kgy4n-00077h-Gp for geh-help-gnu-emacs@m.gmane.org; Sat, 20 Sep 2008 04:44:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kgy4O-00076w-Bq for help-gnu-emacs@gnu.org; Sat, 20 Sep 2008 04:44:00 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kgy4N-00076H-NW for help-gnu-emacs@gnu.org; Sat, 20 Sep 2008 04:43:59 -0400 Original-Received: from [199.232.76.173] (port=34280 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kgy4N-00075y-BY for help-gnu-emacs@gnu.org; Sat, 20 Sep 2008 04:43:59 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:3625 helo=mail.muc.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kgy4M-00071n-Dq for help-gnu-emacs@gnu.org; Sat, 20 Sep 2008 04:43:59 -0400 Original-Received: (qmail 64077 invoked by uid 3782); 20 Sep 2008 08:43:55 -0000 Original-Received: from acm.muc.de (pD9E52252.dip.t-dialin.net [217.229.34.82]) by colin2.muc.de (tmda-ofmipd) with ESMTP; Sat, 20 Sep 2008 10:43:53 +0200 Original-Received: (qmail 3335 invoked by uid 1000); 20 Sep 2008 08:50:00 -0000 Content-Disposition: inline In-Reply-To: <823901dd-c54c-4e3b-b6ad-512d52724a46@z11g2000prl.googlegroups.com> User-Agent: Mutt/1.5.9i X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) X-Primary-Address: acm@muc.de X-detected-operating-system: by monty-python.gnu.org: FreeBSD 4.6-4.9 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:57843 Archived-At: Hi, Xah. One small but important point you made: On Thu, Sep 18, 2008 at 04:50:50PM -0700, Xah Lee wrote: > Here are few minor reasons: > * When the scratch buffer is closed, emacs does not prompt user to > save it. This easily causes data loss. The other side of the argument is that *scratch* is intended for temporary, unimportant doodling, and for anybody who uses it this way, being continually prompted to save it would rapidly become annoying. I don't think there's a built in option to change this. However, you could write a hook function to add in this check. The hook is `kill-buffer-query-functions' and is documented in the Elisp manual on the page "Killing Buffers". [ .... ] > * modern_operations.el. A small point about this file (at ): you don't really need the function `kill-line-backwards', since M-0 C-k will do this for you. However, that key binding is a bit clumsy. You could use it like this: (defun kill-line-backwards () "Doc string ...." (interactive) (kill-line 0)) > Xah -- Alan Mackenzie (Nuremberg, Germany).