From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: fancy splash screen Date: Fri, 15 Sep 2006 09:43:26 -0700 Message-ID: References: <85d59xxfp2.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1158338645 22457 80.91.229.2 (15 Sep 2006 16:44:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 15 Sep 2006 16:44:05 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 15 18:44:01 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GOGn8-0006Ud-JU for ged-emacs-devel@m.gmane.org; Fri, 15 Sep 2006 18:43:50 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GOGn7-0006JL-Vp for ged-emacs-devel@m.gmane.org; Fri, 15 Sep 2006 12:43:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GOGms-0006DN-Qj for emacs-devel@gnu.org; Fri, 15 Sep 2006 12:43:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GOGmq-00068K-MS for emacs-devel@gnu.org; Fri, 15 Sep 2006 12:43:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GOGmq-00068F-Gx for emacs-devel@gnu.org; Fri, 15 Sep 2006 12:43:32 -0400 Original-Received: from [148.87.113.118] (helo=rgminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1GOGp2-0006kU-R0 for emacs-devel@gnu.org; Fri, 15 Sep 2006 12:45:49 -0400 Original-Received: from rgmsgw02.us.oracle.com (rgmsgw02.us.oracle.com [138.1.186.52]) by rgminet01.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id k8FGhT8e018736 for ; Fri, 15 Sep 2006 10:43:29 -0600 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-83-5.vpn.oracle.com [141.144.83.5]) by rgmsgw02.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k8FGhSob013583 for ; Fri, 15 Sep 2006 10:43:29 -0600 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <85d59xxfp2.fsf@lola.goethe.zz> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:59882 Archived-At: > > "Emacs" in "About Emacs" is not redundant in any way. > > If you have multiple buffers, there is nothing that > > implies that one named only "About" has help about Emacs. > > Most applications I know have exactly one "About" menu, > and Emacs does not seem to be different in that respect. > > It's not about the menu; it's about the buffer name. There are lots > of buffers whose content is "about" something, and some Emacs > libraries might use that term in buffer names, for various > purposes. You might have buffers "*About Foo Bar*" and "*About > Toto*". But we don't have any such buffers. This seems academical. "We" who? Users may use such buffers. Other libraries may use such buffers. > The buffer about Emacs should be called "*About Emacs*" (possibly > with "GNU"). A buffer name of just "*About*" does not clearly > indicate what it is. As I said: having a single "About" item is common for applications. As I said, it's not about the menu-item name, or the number of menu items per application, or the number of applications; it's about the buffer name. Since the menu entry is called "About Emacs", calling the buffer "*About Emacs*" seems a suitable choice. So we agree. I don't find your arguments for that name persuasive at all, but since I am fine with that choice, it seems useless to haggle over just _why_. Good. > Similarly, I don't see it mentioned in the Emacs manual. Shouldn't > it be mentioned along with the use of space as first character for > internal buffers (e.g. in node Select Buffer)? Node Buffers is > perhaps a good place to mention use of both `*' and initial space in > buffer names. That node gives examples of `*' buffers, without ever > pointing out that they are buffers that are not normally visiting > files. It is basically only a convention, but it might be worth mentioning there or somewhere else. It should be mentioned in the conventions section of the Elisp manual, if it is a convention that we would like programmers to use. If it is useful for users to understand this naming convention (and it must be; otherwise, why use it for user-visible names?), then it should also be pointed out in the Emacs manual.