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: Tue, 28 Apr 2015 19:52:52 +0100 Message-ID: References: <87383xk4ia.fsf@taylan.uni.cx> <87d22zi69k.fsf@taylan.uni.cx> <87a8xtoq3a.fsf@gmail.com> <87sibkemtw.fsf@gmail.com> <87618gem24.fsf@gmail.com> <85tww0w9nm.fsf@iznogoud.viz> <93070d16-c58a-4972-96b5-8fafb81cbd9a@default> <85h9s0w44i.fsf@iznogoud.viz> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1430247182 21699 80.91.229.3 (28 Apr 2015 18:53:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 Apr 2015 18:53:02 +0000 (UTC) To: Drew Adams , Oleh Krehel , Artur Malabarba , emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 28 20:53:01 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 1YnAct-00031Z-Sw for ged-emacs-devel@m.gmane.org; Tue, 28 Apr 2015 20:53:00 +0200 Original-Received: from localhost ([::1]:35491 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnAct-0006eW-7N for ged-emacs-devel@m.gmane.org; Tue, 28 Apr 2015 14:52:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52329) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnAcp-0006eG-QN for emacs-devel@gnu.org; Tue, 28 Apr 2015 14:52:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnAco-00009i-TW for emacs-devel@gnu.org; Tue, 28 Apr 2015 14:52:55 -0400 Original-Received: from mail-la0-x236.google.com ([2a00:1450:4010:c03::236]:34838) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnAco-00009b-LP for emacs-devel@gnu.org; Tue, 28 Apr 2015 14:52:54 -0400 Original-Received: by labbd9 with SMTP id bd9so3161203lab.2 for ; Tue, 28 Apr 2015 11:52:53 -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:content-type; bh=4IrMhkGcSv39/4i27q4Ns5CO+wscf2JLgAuXpV8KoWA=; b=tSFedk95G53tI1y5wvL7RUymVsqQX2MY/g/WoT8MDqIjjpPClbfZMpNPIm9UFt82Fz b2uE1fmLc7ZmWFlHXer7eQf4U3BjGyBL4HzdwE4n1l8ZlPkO/Bq1BL5uiLhW5dPk5T64 GU2FqlqXF6iItzS+G7jgz64MFwbWQg4HVWGZ6/u48oDldAxGBzbwpESYNydzAAe44O7Y gREmTb7XNhaAfMECJzCKTrzC5BfkyPUjIjM564HfDL6RwM9tM/gdbOXQxNXLuwTmf8uP qc+M7iAiN/bOA7E+SY0tdPXPaQiS21J/xMgXt9DSIQCllaiNGbu8EWBD4OMIuu9aNsAk rSKQ== X-Received: by 10.112.97.202 with SMTP id ec10mr15713210lbb.4.1430247172933; Tue, 28 Apr 2015 11:52:52 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Tue, 28 Apr 2015 11:52:52 -0700 (PDT) In-Reply-To: <85h9s0w44i.fsf@iznogoud.viz> X-Google-Sender-Auth: rafUfsomt-4P3GNTzDOsYyvJ7GA X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::236 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:185981 Archived-At: 2015-04-28 18:29 GMT+01:00 Wolfgang Jenkner : > On Tue, Apr 28 2015, Drew Adams wrote: > >> Doesn't sound like a great idea, to me. (Perhaps it was a joke?) > > Not at all. > > The purpose is to clearly indicate that setting or binding the variable > in the straightforward (and normal, if you will) way won't work. I wouldn't oppose having `describe-variable' add a short sentence in the same place where it says things like "becomes buffer local" or "is risky". The sentence could be as short as: this variable has a `custom-set' property; perhaps followed by something else such as so setting it directly might not have any effect But I don't think printing the entire custom-set property is desirable.