unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] Remove special requirement to disable startup message.
Date: Tue, 22 Dec 2015 11:39:02 -0800	[thread overview]
Message-ID: <m21tae9stl.fsf@newartisans.com> (raw)
In-Reply-To: <20151222184106.GA5310@holos> (Mark Oteiza's message of "Tue, 22 Dec 2015 13:41:06 -0500")

[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]

>>>>> Mark Oteiza <mvoteiza@udel.edu> writes:

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

I'm not sure how to reach a "good" level in explaining this, but here is the
main idea: Emacs is a flagship of the GNU project, whose primary goal is to
ensure software freedom for users, rather than merely to provide software to
users.

Thus, when Emacs starts up, one of its goals, as a GNU project, is not only to
edit files, but to make people aware of the issues of software freedom. (This
is also why Nicolas is currently having discussions with Richard about text to
be added to the Emacs web page that ostensibly has little to do with Emacs as
a software project.)

If you think in terms of technical merit alone, there are more than a few
things about this project, and participating in its development, that do not
make complete sense, nor have "good" explanations. You have to broaden the
scope to include the issue of promoting software freedom, and how Emacs is
used to help achieve that task, for all the pieces to fall into place.

Note that this is free software after all: You could fork Emacs and remove
this code. But that wouldn't be GNU Emacs; and GNU Emacs strives very hard to
ensure that the question of software freedom is never buried or side-lined.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]

  reply	other threads:[~2015-12-22 19:39 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 [this message]
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=m21tae9stl.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mvoteiza@udel.edu \
    --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).