From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark Oteiza Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Remove special requirement to disable startup message. Date: Wed, 23 Dec 2015 20:41:22 -0500 Message-ID: <20151224014122.GA19782@holos> References: <878u4qdpd4.fsf@udel.edu> <20151222184106.GA5310@holos> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1450921302 26740 80.91.229.3 (24 Dec 2015 01:41:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 24 Dec 2015 01:41:42 +0000 (UTC) To: John Wiegley , Richard Stallman , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 24 02:41:37 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aBuuN-00011a-OY for ged-emacs-devel@m.gmane.org; Thu, 24 Dec 2015 02:41:35 +0100 Original-Received: from localhost ([::1]:58570 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aBuuM-0004yH-TV for ged-emacs-devel@m.gmane.org; Wed, 23 Dec 2015 20:41:34 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aBuuJ-0004yB-4o for emacs-devel@gnu.org; Wed, 23 Dec 2015 20:41:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aBuuE-0004CF-DQ for emacs-devel@gnu.org; Wed, 23 Dec 2015 20:41:31 -0500 Original-Received: from mail-qg0-x230.google.com ([2607:f8b0:400d:c04::230]:36240) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aBuuE-0004C9-8U for emacs-devel@gnu.org; Wed, 23 Dec 2015 20:41:26 -0500 Original-Received: by mail-qg0-x230.google.com with SMTP id c96so145228634qgd.3 for ; Wed, 23 Dec 2015 17:41:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=udel-edu.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=TBj/fftPb7yYxKxFI2CAYhJhdn+c9kFxyRIbOoiKaFU=; b=OAjq6trSttHS8lBbCHlwYG6Uf84196MPKHqY4OIqQnrWl3IwWCirqOF/0+5ClbF97h zuida9fbZcbRIxDlclQU1RZYL/NXrnKPtmeBrpVIdxtHEz48NDcaeKWERIaTOphs/vd/ Q31VIyMkbhHKpCtQoE+M9NOZW20pKXjEbjxIJ3mWKSC23x2uDNd2ziJgIEBh9XBBQi0a s7eM/hKq+DR9QXgC5d6zRJVuP9CIJ84vtBk2rK11+M8ZOizUvihf3qQszfNus78du4Ar NC9TsrXSWHPrCXjYsS+/7yUk0UoaocF4qCY7X/te0+h2JTE4Px1SGh2spe2M39TXTIb4 smkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=TBj/fftPb7yYxKxFI2CAYhJhdn+c9kFxyRIbOoiKaFU=; b=F8KZ8xiK2KLH5WE11RlvppunxO8CoSzsgmkdcfLsGn8A7Px7AB0GGRr41gF5jBk+Rh p2GandCesvh1pkC/9Vf+w5aAMR8kj4Cu1weBfwyD2BHPXxdtzNaoEhaYqhTtmNzv3jkE Cl8vcui1WQxS3+cm2Gpwv4rZYnbEOrddWBqRvPWCKTplyRoMl3FIX01IfEzW6bKaHPHC p2v0KQJKfIRmsGq+M1mLOIMGWmD3VOG2UFBvxCv4zRrf9UwHMUZwQhABZHiQfAufYPhE uQmlW5adW6n/twfZcDHrdFxY9b4ht5r99Pq+Oe+pTfarrjTDZSYdNIh7fv2487Cgvs4F s4GA== X-Gm-Message-State: ALoCoQnAmu5EVJnNZHGrwxhxBIhcn/B5AUPgtWbRRcRjARnfrqSbFZf6EYlMD0mylZzshQNvZu0J2ZQrm/ptYJzKty9PYDlrhw== X-Received: by 10.140.148.75 with SMTP id 72mr47579162qhu.13.1450921285405; Wed, 23 Dec 2015 17:41:25 -0800 (PST) Original-Received: from holos.localdomain (c-73-172-248-173.hsd1.md.comcast.net. [73.172.248.173]) by smtp.gmail.com with ESMTPSA id g10sm19252535qkb.26.2015.12.23.17.41.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Dec 2015 17:41:24 -0800 (PST) Original-Received: by holos.localdomain (Postfix, from userid 1000) id 9086C696AD; Wed, 23 Dec 2015 20:41:22 -0500 (EST) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24+44 (9480a363a68a) (2015-08-30) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c04::230 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196742 Archived-At: On 22/12/15 at 11:39am, John Wiegley wrote: > >>>>> Mark Oteiza 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. Yes, this is why the splash screen and echo area message are on by default. There's also a help menu populated by all the items shown in the splash. The splash is easy to disable, and the elisp manual instructs not to disable it site wide. But the single redundant line in *Messages* is somehow exceedingly more important to merit obfuscation shared by _nothing else_ in Emacs. These two variables, inhibit-startup-screen and inhibit-startup-echo-area-message, facilitate passing on the same exact information and are treated wildly differently. I'm not suggesting changing the defaults, rather removing an outlier in Emacs customization that is silly in implementation (it's fragile) and motivation (it's redundant). To suggest that this defcustom keeps a user, power user, programmer, distro packager, site admin, etc. from achieving the theoretical desire of hiding information about Emacs or GNU from themselves or their system's users is dubious. Anything from an idle search engine query to searching debbugs or comprehending the source will yield a workaround. > 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. Forking? Wholly unnecessary, as the previous discussions regarding startup-inhibit-echo-area-message have shown.