From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@newcastle.ac.uk (Phillip Lord) Newsgroups: gmane.emacs.help Subject: Re: using use-package Date: Fri, 14 Aug 2015 10:35:15 +0100 Message-ID: <871tf6dxgs.fsf@newcastle.ac.uk> References: <67cb463e-41f6-4f37-91ee-15d0fdb5ba9f@googlegroups.com> <20150812180621.32265.2E673ABE@ahiker.mooo.com> <87bnebnyyl.fsf@newcastle.ac.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1439544946 26600 80.91.229.3 (14 Aug 2015 09:35:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Aug 2015 09:35:46 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Aug 14 11:35:46 2015 Return-path: Envelope-to: geh-help-gnu-emacs@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 1ZQBOq-0003Yk-Q8 for geh-help-gnu-emacs@m.gmane.org; Fri, 14 Aug 2015 11:35:44 +0200 Original-Received: from localhost ([::1]:45355 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQBOq-00061A-4H for geh-help-gnu-emacs@m.gmane.org; Fri, 14 Aug 2015 05:35:44 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQBOV-0005yJ-7n for help-gnu-emacs@gnu.org; Fri, 14 Aug 2015 05:35:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZQBOP-0006Eu-Le for help-gnu-emacs@gnu.org; Fri, 14 Aug 2015 05:35:23 -0400 Original-Received: from cheviot22.ncl.ac.uk ([128.240.234.22]:57459) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQBOP-0006Eq-FH for help-gnu-emacs@gnu.org; Fri, 14 Aug 2015 05:35:17 -0400 Original-Received: from smtpauth-vm.ncl.ac.uk ([10.8.233.129] helo=smtpauth.ncl.ac.uk) by cheviot22.ncl.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1ZQBOO-0004f7-Dt; Fri, 14 Aug 2015 10:35:16 +0100 Original-Received: from jangai.ncl.ac.uk ([10.66.67.223] helo=localhost) by smtpauth.ncl.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1ZQBOO-0000jl-5v; Fri, 14 Aug 2015 10:35:16 +0100 In-Reply-To: (Stefan Monnier's message of "Thu, 13 Aug 2015 12:15:20 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 128.240.234.22 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:106578 Archived-At: Stefan Monnier writes: >> I'm still trying to scope what you are after, though. Are you interested >> only in those features which can never overlap with ELPA? Or only in >> those features will necessarily overlap with ELPA. > > Not sure either. Maybe I'm looking for something like use-package but > which takes better advantage of ELPA. Over and above the "ensure" keyword which does take advantage of ELPA. > Maybe also one that better integrates with Customize. This is something that I think would be nice, but is actually independent of use-package. I'd love to be able to do something like (custom-setq my-variable 10) which sets the variable, but does not result in the "the value of this variable has been changed outside of customize" message in Custom. And also (configurable) which errors if my-variable is typed as a string in custom. > I guess I'm also interested to see what other users find important in > terms of "configuration problems that need solving". > > Maybe one other aspect is the issue of bootstrap/ordering between > package.el and Customize: we want to be able to customize package.el via > Customize (and some of these settings may need to be set before > package-initialize), but the one-and-only call to custom-set-variables > often needs to be done after package-initialize. So, splitting the > config "by package" is probably the right way to go about it. I can see this is a problem, but haven't got anything to suggest I am afraid. Phil