From: Mark Oteiza <mvoteiza@udel.edu>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Remove special requirement to disable startup message.
Date: Tue, 22 Dec 2015 13:41:06 -0500 [thread overview]
Message-ID: <20151222184106.GA5310@holos> (raw)
In-Reply-To: <E1aAWJf-0007QW-1q@fencepost.gnu.org>
On 20/12/15 at 12:13am, Richard Stallman wrote:
> This code blocks the most obvious way for the site to disable the
> message for all users.
Why is this important?
It also makes the init file of a user following the docstring of
inhibit-startup-echo-area-message less portable. Further, it forces
particular syntax upon users not using the customize interface.
> That's exactly what it is meant to do. When
> this doesn't work, the person will investigate why not, read what we
> said about the issue, and may decide not to do it.
I have yet to see a good explanation for the weird treatment of this
variable. "Preventing site from disabling the message" is silly because
you cannot prevent it. "thoughtless copying of init files" is another
silly reason because the init file can contain elisp that
unconditionally disables the message.
next prev parent reply other threads:[~2015-12-22 18:41 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 [this message]
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
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
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=20151222184106.GA5310@holos \
--to=mvoteiza@udel.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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).