From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: fancy splash screen
Date: Fri, 15 Sep 2006 17:21:28 +0200 [thread overview]
Message-ID: <85psdxxiiv.fsf@lola.goethe.zz> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMIEGACLAA.drew.adams@oracle.com> (Drew Adams's message of "Fri\, 15 Sep 2006 07\:12\:11 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> >> BTW, I'd prefer calling the "GNU Emacs" buffer either
> >> "*splash-screen*" or " *splash-screen*".
> > Or "*About Emacs*"...
>
> Emacs is somewhat redundant.
> *About* would probably be fine.
>
> "About Emacs" describes what it is. "About GNU Emacs" would be
> better, providing a helpful reminder about GNU (but some will argue
> that GNU is never needed in "GNU Emacs").
It is not needed in general. It can be nice to stress its role in the
GNU project when talking about that, but I think that in purely
technical contexts, just "Emacs" is the more straightforward use.
> "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.
> Is it good or bad to use "*...*"? I don't know. I tend to think it's
> not needed here.
Standard naming convention for buffers without associated files.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-09-15 15:21 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 [this message]
2006-09-15 16:00 ` Drew Adams
2006-09-15 16:22 ` David Kastrup
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=85psdxxiiv.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).