From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: RE: Calling (package-initialize) sooner during initialization Date: Sun, 19 Apr 2015 01:38:18 +0100 Message-ID: References: <87383xk4ia.fsf@taylan.uni.cx> <55329AD9.4090303@yandex.ru> <87lhhpi9ns.fsf@taylan.uni.cx> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e012291a29bafb8051409072f X-Trace: ger.gmane.org 1429403906 17785 80.91.229.3 (19 Apr 2015 00:38:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 19 Apr 2015 00:38:26 +0000 (UTC) Cc: =?UTF-8?B?VGF5bGFuIFVscmljaCBCYXnEsXJsxLEvS2FtbWVy?= , Dmitry Gutov , Stefan Monnier , emacs-devel To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 19 02:38:25 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 1YjdFh-0007pV-I5 for ged-emacs-devel@m.gmane.org; Sun, 19 Apr 2015 02:38:25 +0200 Original-Received: from localhost ([::1]:47207 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjdFg-0005H8-IC for ged-emacs-devel@m.gmane.org; Sat, 18 Apr 2015 20:38:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjdFc-0005H0-UK for emacs-devel@gnu.org; Sat, 18 Apr 2015 20:38:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjdFb-000067-TI for emacs-devel@gnu.org; Sat, 18 Apr 2015 20:38:20 -0400 Original-Received: from mail-la0-x229.google.com ([2a00:1450:4010:c03::229]:33476) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjdFb-00005w-K0 for emacs-devel@gnu.org; Sat, 18 Apr 2015 20:38:19 -0400 Original-Received: by layy10 with SMTP id y10so103883026lay.0 for ; Sat, 18 Apr 2015 17:38:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ewjC7D1PQ2R9jzkcLmq8zZx9wMu0BdAZv2SpOMPQk34=; b=xAqAeM8mZFJhenACa+rir7Pjz40sFi9bejrrigRBbRjEzaU7T8PuTwtZnCCeAxGOfp L2F6EZtsDXDELxzkO0jj7kQdljeqzyNr5sSJ9A+W6Z1aq2sH6Anoem32NiL9uQHO06ei gs3FjgYr3dhsQLb0OMYA/kASYCF0YmU0wUzjFbPhet5QUl1Ij+LZnBQC6xtTtylnxcCu XvwJvVVhFjFbxtheZ8h6DlsZiYT1VEw2poxlBrQ5V+/axxWnTGMN1jOIHXzwmvbGhZ+S v4MNnuxaXiqMgSJOIaa/wxhvyMBBKvmrXIHs9gQfHb/2plmjr+1cD0vknyzyVVjlemTt Hp9A== X-Received: by 10.152.2.105 with SMTP id 9mr9945523lat.16.1429403898456; Sat, 18 Apr 2015 17:38:18 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Sat, 18 Apr 2015 17:38:18 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Sat, 18 Apr 2015 17:38:18 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: 6m5uvrLrBJVrZZ43H3XEGXDZoqU X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::229 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:185645 Archived-At: --089e012291a29bafb8051409072f Content-Type: text/plain; charset=UTF-8 On Apr 19, 2015 1:24 AM, "Drew Adams" wrote: > > > I usually tell people to place their custom-set-variables at the top > > of their init file. > > Sorry, but any such advice is misguided, IMO. > > There is simply no such one-size-fits-all rule wrt when Customize > settings should be made. I agree 100%, there's no right order that will cover every case. I was just saying that keeping it at the top avoids a common problem with themes. It's not something I advocate religiously, it's just something I tell new users when they run into this theme issue. > > 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. Again, agreed. --089e012291a29bafb8051409072f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Apr 19, 2015 1:24 AM, "Drew Adams" <drew.adams@oracle.com> wrote:
>
> > I usually tell people to place their custom-set-variables at the = top
> > of their init file.
>
> Sorry, but any such advice is misguided, IMO.=C2=A0
>
> There is simply no such one-size-fits-all rule wrt when Customize
> settings should be made.=C2=A0

I agree 100%, there's no right order that will cover eve= ry case. I was just saying that keeping it at the top avoids a common probl= em with themes. It's not something I advocate religiously, it's jus= t something I tell new users when they run into this theme issue.

> > 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.=C2=A0 That is one consideration. > There are others.=C2=A0 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.

Again, agreed.

--089e012291a29bafb8051409072f--