unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: fancy splash screen
Date: Fri, 15 Sep 2006 18:22:33 +0200	[thread overview]
Message-ID: <85d59xxfp2.fsf@lola.goethe.zz> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMAEGCCLAA.drew.adams@oracle.com> (Drew Adams's message of "Fri\, 15 Sep 2006 09\:00\:32 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

>     > "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.

> 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.
Since the menu entry is called "About Emacs", calling the buffer
"*About Emacs*" seems a suitable choice.  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_.

> 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.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-09-15 16:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  8:45 fancy splash screen martin rudalics
2006-09-14 17:47 ` Chong Yidong
2006-09-15  3:14 ` Richard Stallman
2006-09-15 12:19   ` martin rudalics
2006-09-15 13:02     ` Romain Francoise
2006-09-15 13:06       ` David Kastrup
2006-09-15 14:12         ` martin rudalics
2006-09-15 15:17           ` David Kastrup
2006-09-16 19:05             ` Richard Stallman
2006-09-15 14:12         ` Drew Adams
2006-09-15 15:21           ` David Kastrup
2006-09-15 16:00             ` Drew Adams
2006-09-15 16:22               ` David Kastrup [this message]
2006-09-15 16:43                 ` Drew Adams
2006-09-15 22:57     ` Richard Stallman
2006-09-15 22:57     ` Richard Stallman
2006-09-16 12:55       ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85d59xxfp2.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).