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: Wed, 23 Dec 2015 20:41:31 -0500 [thread overview]
Message-ID: <20151224014131.GA19087@holos> (raw)
In-Reply-To: <E1aBbhD-0000Cp-ST@fencepost.gnu.org>
On 23/12/15 at 12:10am, Richard Stallman wrote:
> > > This code blocks the most obvious way for the site to disable the
> > > message for all users.
>
> > Why is this important?
>
> So that sysadmins will think twice before disabling the message for
> their users.
Are there sites that disable the message? Is there something other than
imagining hostile site admins or distro packagers that prompted the
addition (and consequent bizarre treatment) of this variable?
> > It also makes the init file of a user following the docstring of
> > inhibit-startup-echo-area-message less portable.
>
> In what sense "less portable"? What does it need to be portable to?
> If you answer that, we can judge whether this issue matters.
An individual using their username to disable the message will not
necessarily be able to use the same config across different sites.
The practice of keeping emacs configs synchronized across sites is
rather prevalent, and this weird treatment of the variable makes it
useless as a defcustom in this respect. Put another way, the message is
not "easily inhibitable" as written in the Elisp manual.
next prev parent reply other threads:[~2015-12-24 1: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
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 [this message]
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=20151224014131.GA19087@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).