From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Calling (package-initialize) sooner during initialization Date: Sat, 18 Apr 2015 17:24:20 -0700 (PDT) Message-ID: References: <87383xk4ia.fsf@taylan.uni.cx> <55329AD9.4090303@yandex.ru> <87lhhpi9ns.fsf@taylan.uni.cx> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1429403110 8059 80.91.229.3 (19 Apr 2015 00:25:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 19 Apr 2015 00:25:10 +0000 (UTC) Cc: Dmitry Gutov , Stefan Monnier , emacs-devel To: bruce.connor.am@gmail.com, =?utf-8?B?VGF5bGFuIFVscmljaCBCYXnEsXJsxLEvS2FtbWVy?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 19 02:24:56 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 1Yjd2c-0007Vw-9R for ged-emacs-devel@m.gmane.org; Sun, 19 Apr 2015 02:24:54 +0200 Original-Received: from localhost ([::1]:47195 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yjd2a-0003Qe-Qi for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 20:24:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37909) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yjd2P-0003QW-9v for emacs-devel@gnu.org; Sat, 18 Apr 2015 20:24:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yjd2M-0005OY-4p for emacs-devel@gnu.org; Sat, 18 Apr 2015 20:24:41 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:24700) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yjd2L-0005Ml-Ti for emacs-devel@gnu.org; Sat, 18 Apr 2015 20:24:38 -0400 Original-Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t3J0OTaR031469 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 19 Apr 2015 00:24:30 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.13.8/8.13.8) with ESMTP id t3J0ORNX000433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 19 Apr 2015 00:24:28 GMT Original-Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t3J0OR3u027835; Sun, 19 Apr 2015 00:24:27 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: aserv0022.oracle.com [141.146.126.234] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 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:185644 Archived-At: > I usually tell people to place their custom-set-variables at the top > of their init file.=20 Sorry, but any such advice is misguided, IMO. Depending on one's init file (including what particular libraries are loaded, and when), it can make sense to load `custom-file' (the equivalent of, but wiser than, positioning `custom-set-variables') in any number of places in the file. There is simply no such one-size-fits-all rule wrt when Customize settings should be made. If those fiddling now with redesigning package setup think there is, then I fear we are in for a world of trouble. Dunno whether this is the kind of thing Nic was thinking of, but it's what I worry about. My suggestion: Don't try to be too clever. Keep it simple. Which is another way of saying avoid simplistic assumptions. > Otherwise, if you install a new theme and try to > `(load-theme 'theme-name)' in your init file, you'll get problems > because `custom-safe-themes' hasn't been set yet. Welcome to the world of Customize. That is one consideration. There are others. You will not find a simple rule such as you are suggesting that works in general, precisely because what else is in the init file matters.