unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Remove special requirement to disable startup message.
Date: Sun, 20 Dec 2015 00:13:55 -0500	[thread overview]
Message-ID: <E1aAWJf-0007QW-1q@fencepost.gnu.org> (raw)
In-Reply-To: <878u4qdpd4.fsf@udel.edu> (message from Mark Oteiza on Sat, 19 Dec 2015 17:51:03 -0500)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > * lisp/startup.el (inhibit-startup-echo-area-message): Replace custom
  > string with t.
  > (display-startup-echo-area-message): Only check if
  > inhibit-startup-echo-area-message is truthy.

Please do not make this change.

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

OF COURSE this does actually stop people from disabling the message.
It isn't intended to.  In free software, we cannot actually stop
people from making a certain change.

This code blocks the most obvious way for the site to disable the
message for all users.  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.

Please leave the code alone.

-- 
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.




  reply	other threads:[~2015-12-20  5:13 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 [this message]
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
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=E1aAWJf-0007QW-1q@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mvoteiza@udel.edu \
    /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).