From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xah Lee Newsgroups: gmane.emacs.help Subject: Re: How to get rid of *GNU Emacs* buffer on start-up? Date: Fri, 19 Sep 2008 17:02:11 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <873ajzwoqu.fsf@kobe.laptop> <823901dd-c54c-4e3b-b6ad-512d52724a46@z11g2000prl.googlegroups.com> <87ljxoffs6.fsf@atthis.clsnet.nl> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1221871250 21083 80.91.229.12 (20 Sep 2008 00:40:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 20 Sep 2008 00:40:50 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Sep 20 02:41:46 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 1KgqXg-0003fq-R3 for geh-help-gnu-emacs@m.gmane.org; Sat, 20 Sep 2008 02:41:45 +0200 Original-Received: from localhost ([127.0.0.1]:38994 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KgqWf-0007Rt-DU for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Sep 2008 20:40:41 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!i20g2000prf.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 58 Original-NNTP-Posting-Host: 24.6.185.159 Original-X-Trace: posting.google.com 1221868931 26419 127.0.0.1 (20 Sep 2008 00:02:11 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sat, 20 Sep 2008 00:02:11 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: i20g2000prf.googlegroups.com; posting-host=24.6.185.159; posting-account=qPxGtQkAAADb6PWdLGiWVucht1ZDR6fn User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.2 Safari/525.22, gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:162482 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:57823 Archived-At: On Sep 19, 9:13 am, Nikolaj Schumacher wrote: > We just call them (scratch) buffers. They provide all the > same featuresXah's"untitled files" do. Really, the only differences are > nomenclature, the way of creating them and the fact that one exists by > default. That's not the only differences. I have given detail on other differences. Quote from my article: http://xahlee.org/emacs/modernization_scratch_buffer.html =C2=AB =E2=80=A2 There is no easy, intuitive way to create multiple scratch buffer= s. (it is done by using the switch-to-buffer command (C-x b) and give name that is not one of existing buffers.) =E2=80=A2 Emacs does not provide a user level function to create a new buff= er. It has menu =E2=80=9CFile=E2=80=A3Open file...=E2=80=9D (a wrapper to the f= ind-file command), which immediately prompt user for a full file path. This is annoying. Modern apps's New File command actually just create a new untitled file without prompting, and only when user save it it prompt a file name. If user closes it, it prompts for saving. =C2=BB and quote from my post here: I don't agree that emacs does provide a user-level function for creating a new buffer. The 2 practical methods to create a new buffer, by find-file or switch-to-buffer, are both not designed to create a new buffer for temp use, and each has serious problems in my opinion. =E2=80=A2 There is no easy, intuitive way to create multiple scratch buffer= s. (it is done by using the switch-to-buffer command (C-x b) and give name that is not one of existing buffers.) =E2=80=A2 Emacs does not provide a user level function to create a new buffer. It has =E2=80=9COpen file...=E2=80=9D (a wrapper to the find-file = command), which immediately prompt user for a full file path. This is annoying. Modern apps's New File command actually just create a new untitled file without prompting, and only when user save it it prompt a file name. If user closes it, it prompts for saving. In summary: the problem with find-file is that it promps user to enter a file name upfront. The problem with switch-to-buffer is that it doesn't promp to save when user closes it. In both, the functions are simply not designed for creating a new temp buffer. Xah =E2=88=91 http://xahlee.org/ =E2=98=84