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 19:58:55 -0700 (PDT) Organization: http://groups.google.com Message-ID: <71208e97-140c-445d-8eda-1705f11b14b3@r15g2000prd.googlegroups.com> 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 1221882088 23263 80.91.229.12 (20 Sep 2008 03:41:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 20 Sep 2008 03:41:28 +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 05:42:24 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 1KgtMV-0004yu-1H for geh-help-gnu-emacs@m.gmane.org; Sat, 20 Sep 2008 05:42:23 +0200 Original-Received: from localhost ([127.0.0.1]:54299 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KgtLT-0004SA-KK for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Sep 2008 23:41:19 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!r15g2000prd.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 52 Original-NNTP-Posting-Host: 24.6.185.159 Original-X-Trace: posting.google.com 1221879536 27238 127.0.0.1 (20 Sep 2008 02:58:56 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sat, 20 Sep 2008 02:58:56 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: r15g2000prd.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:162493 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:57836 Archived-At: On Sep 19, 7:35 pm, Kevin Rodgers wrote: > XahLeewrote: > > 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 bu= ffers. > > (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-f= ile 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. > > Wow, if you had put 1% of the effort into coding that you put into this > thread, you could have come up with something like this: > > (defun switch-to-new-buffer () > "Switch to a new *scratch* buffer." > (interactive) > (switch-to-buffer (generate-new-buffer "*scratch*")) > (setq switch-to-new-buffer t)) > > If it's such a huge problem for 99% of users, you could propose to the > maintainers that it be added to files.el Thanks. But the issue is not about how to code a better switch-to-new- buffer. The issue is about criticism of *scratch* buffer, and a suggestion that emacs should remove it. Please see: http://en.wikipedia.org/wiki/Critical_thinking If you didn't read the original article, please see: http://xahlee.org/emacs/modernization_scratch_buffer.html Xah =E2=88=91 http://xahlee.org/ =E2=98=84