From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Remove special requirement to disable startup message.
Date: Tue, 22 Dec 2015 14:09:49 -0500 [thread overview]
Message-ID: <20151222190949.GB5310@holos> (raw)
In-Reply-To: <83si2xt967.fsf@gnu.org>
On 20/12/15 at 05:46pm, Eli Zaretskii wrote:
> > From: Mark Oteiza <mvoteiza@udel.edu>
> > Date: Sat, 19 Dec 2015 17:51:03 -0500
> >
> > After seeing a commentary on the variable here:
> >
> > http://emacshorrors.com/posts/advertising-your-freedom.html
> >
> > and reading bug#13208 and bug#12370, I am inclined to change this
> > behavior. Not only is the checking mechanism in
> > `display-startup-echo-area-message' naïve and error-prone (see
> > bug#13208), but it does nothing to stop the site from disabling the
> > message, which is the only tangible justification (found in bug#12730)
> > for the special treatment to exist. It is trivial for site-start.el,
> > default.el, or init.el to contain
> >
> > (defun display-startup-echo-area-message () nil)
> >
> > or similar to disable the message for all users (example from bug#13208).
>
> I'm sorry, but I don't agree with the emacshorrors commentary, and I
> don't think we should make disabling this startup message site-wide so
> easy. The discussion in bug#12370 shows I'm not the only one.
What the discussion fails to show is why this is desirable.
I'm also not the only one asking why such weird treatment is present.
;; FIXME? Why does this get such weirdly extreme treatment, when the
;; more important inhibit-startup-screen does not.
This was added before either bug#12370 or bug#13208 were filed; the
answers in all of these discussions have been incomplete.
> (Splash screen is different: it shows information useful to first-time
> Emacs users, whereas the echo-area message is about the GNU system and
> the software freedom.)
The echo-area message simply points out the keybinding to show the
splash screen.
> I appreciate your efforts in producing a patch for review, but I'd
> rather encourage development in the other direction:
>
> . make sure display-startup-echo-area-message cannot be so easily
> redefined or advised (up to some practical limit)
>
> . allow the value to be a list of strings, each one a user name, and
> prevent the echo-area message from being displayed if the user
> name is one of these strings -- this should take care of the use
> case in bug#12370
>
> Would you like to work on these enhancements?
Thanks but no thanks. I'm not interested in obfuscating the
customization of Emacs, and have not yet been given any reason why such
a thing is important.
next prev parent reply other threads:[~2015-12-22 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 22:51 [PATCH] Remove special requirement to disable startup message Mark Oteiza
2015-12-20 5:13 ` Richard Stallman
2015-12-22 18:41 ` Mark Oteiza
2015-12-22 19:39 ` John Wiegley
2015-12-24 1:41 ` Mark Oteiza
2015-12-25 5:48 ` Richard Stallman
2015-12-25 16:24 ` Mark Oteiza
2015-12-23 5:10 ` Richard Stallman
2015-12-24 1:41 ` Mark Oteiza
2015-12-24 3:44 ` Eli Zaretskii
2015-12-25 5:48 ` Richard Stallman
2015-12-24 5:07 ` Random832
2015-12-20 15:46 ` Eli Zaretskii
2015-12-22 19:09 ` Mark Oteiza [this message]
2015-12-22 19:27 ` Eli Zaretskii
2015-12-24 1:49 ` Mark Oteiza
2015-12-24 3:45 ` Eli Zaretskii
2016-01-07 0:08 ` Phillip Lord
2016-01-07 0:38 ` John Wiegley
2016-01-07 3:38 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151222190949.GB5310@holos \
--to=mvoteiza@udel.edu \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.