From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?UTF-8?Q?Jorgen_Sch=C3=A4fer?= Newsgroups: gmane.emacs.devel Subject: Re: Calling (package-initialize) sooner during initialization Date: Sun, 12 Apr 2015 16:45:15 +0200 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1428849947 25963 80.91.229.3 (12 Apr 2015 14:45:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Apr 2015 14:45:47 +0000 (UTC) Cc: Vasilij Schneidermann , emacs-devel To: Artur Malabarba Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 12 16:45:42 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 1YhJ8l-0002Cj-5M for ged-emacs-devel@m.gmane.org; Sun, 12 Apr 2015 16:45:39 +0200 Original-Received: from localhost ([::1]:45509 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhJ8k-0005d7-8n for ged-emacs-devel@m.gmane.org; Sun, 12 Apr 2015 10:45:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhJ8P-0005cn-97 for emacs-devel@gnu.org; Sun, 12 Apr 2015 10:45:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YhJ8O-0001s3-GN for emacs-devel@gnu.org; Sun, 12 Apr 2015 10:45:17 -0400 Original-Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:35204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhJ8O-0001rt-9k for emacs-devel@gnu.org; Sun, 12 Apr 2015 10:45:16 -0400 Original-Received: by wgyo15 with SMTP id o15so57803664wgy.2 for ; Sun, 12 Apr 2015 07:45:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3nX+lwFiwLHR6ReDaNBQ/vdemreRRX0kGF3xKEQ+DrQ=; b=tk4eMIalqVHXNK49RGZUfjY3B0R07vk5ed/daj50aVKFkQBAY50b5IjZgEv+HV8Zgc VEhEPgw/nB0rsViOPFs6tl969ZF/d+tyik52+DKU5UOIjvi+tlS2/nH91cJZCYTXyuEB IwdtOEg1UhMU84LzSzOnLuoHAd9jW+hs8tZk6uMAgHM77ua1W9abmJynsT5fC9sbn7iA G0ji1Qpqyt5sQmwELG5M9bjBxb6wO0VO7zlui+pAPXPxuwxRho64T/kwyvTzpjkepYyU r3XXCEJ2aIxAhDmq2Uzf9bJYFBk9d7Z1URzqaMf2EFKnhDtKV7E1mCjJ+byABJAOykXs xcyQ== X-Received: by 10.194.61.133 with SMTP id p5mr19988629wjr.132.1428849915652; Sun, 12 Apr 2015 07:45:15 -0700 (PDT) Original-Received: by 10.27.52.194 with HTTP; Sun, 12 Apr 2015 07:45:15 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22e 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:185339 Archived-At: On Sun, Apr 12, 2015 at 4:26 PM, Artur Malabarba wrote: >>> - package-load-list: Needs to be configured before. >> >> If the user does not want to enable certain packages, they can move >> them out of ~/.emacs.d/elpa/. If necessary, they can move the packages >> into, say, ~/.emacs.d/held/ and run >> (package-load-directory "~/.emacs.d/held") after configuring this variable. > > This sounds very inconvenient for those who don't want to activate a > specific package at startup, but want to keep it up-to-date with > package.el. Not to mention the package won't be seen by package.el and > so won't be considered when dependency checking. The trivial solution to this would be to set package-user-dir to ~/.emacs.d/packages/ in your user init file, configure package-load-list as before, and run (package-load-directory package-user-dir). That's one line more (setting package-user-dir) than it is now, and achieves the same result, so I would not exactly call this "very inconvenient". I have to admit that this seems like a pretty niche use case, though. Out of curiosity, why would you not want the autoloads of an installed package be loaded at startup? What workflow makes this useful? Regards, Jorgen