From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chetan Pandya Newsgroups: gmane.emacs.devel Subject: Re: Autoloaded defcustoms Date: Tue, 6 Jan 2009 10:18:29 -0800 (PST) Message-ID: <377561.61615.qm@web83201.mail.mud.yahoo.com> References: Reply-To: pandyacus@sbcglobal.net NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1231265940 12990 80.91.229.12 (6 Jan 2009 18:19:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Jan 2009 18:19:00 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Juri Linkov , Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 06 19:20:10 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LKGWx-0008LQ-LP for ged-emacs-devel@m.gmane.org; Tue, 06 Jan 2009 19:19:55 +0100 Original-Received: from localhost ([127.0.0.1]:58177 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKGVh-00013y-KD for ged-emacs-devel@m.gmane.org; Tue, 06 Jan 2009 13:18:37 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LKGVd-00013a-FV for emacs-devel@gnu.org; Tue, 06 Jan 2009 13:18:33 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LKGVb-00013M-2x for emacs-devel@gnu.org; Tue, 06 Jan 2009 13:18:33 -0500 Original-Received: from [199.232.76.173] (port=50807 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKGVa-00013J-U4 for emacs-devel@gnu.org; Tue, 06 Jan 2009 13:18:30 -0500 Original-Received: from web83201.mail.mud.yahoo.com ([216.252.101.45]:32847) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LKGVa-0004nz-JT for emacs-devel@gnu.org; Tue, 06 Jan 2009 13:18:30 -0500 Original-Received: (qmail 62447 invoked by uid 60001); 6 Jan 2009 18:18:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=G41n4aqsRZMVotFRQtD/gzvKLQ4jbiCVSV8EaypZObxudLsgGeAfCB1qWSadMx/oGCDYIAE/rNZCqKyMXL/TXoUsXeeRWZX7ZtP2B+o1wb234z1+7rFE5dYd58SsBgDrn2ItvqPzki36sInAdFJV/OSP8k/VXYa4m2HzxOrZMxY=; X-YMail-OSG: vJeeADwVM1mi4OS5xnFajR34x03x9oow._IKhBB0F1Yl8mAIUXD_KRSDEP38OuKbORzByZ8uFhBb40RX21FwKDiPfBpq.Cjjj8JRFMomIaNEXOLuEj5V.JgoN7BcJLEURaZ742CoStGOTis3KbqJneiOh1.4DfjsERize8w_Dg6f4d8r_L3Sb.OdmHfPMAKiSOoEbsM5J54o9u0- Original-Received: from [76.202.61.169] by web83201.mail.mud.yahoo.com via HTTP; Tue, 06 Jan 2009 10:18:29 PST X-Mailer: YahooMailWebService/0.7.218.2 In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107647 Archived-At: --- On Tue, 1/6/09, Lennart Borgman wrote: >> Yes, but the situation I am talking about is that custom-set-variables > >>>> have been run before custom-autoload (see my prev message). > >>> > >>> That would be a pilot error. > >> > >> Yes, but who is the pilot ...? > > > > Catch-22 :-) > > > >> Or, why not take care of this problem? I have no problem giving more > >> concrete examples why this can be needed, but do I have to do that? > > > > Why do you need to run custom-set-variables before custom-autoload? > > This could be during startup of Emacs. There is nothing that says > custom-set-variables should be the last thing there. (And default.el > is run afterwards.) > > Another situation could be if you are trying out a package. Doing that > might require that you run a file with its load defs. You may > customize some variables in that package. The next time you start > Emacs and try this package again those customized variables > will be in a mixed state. You can for example get global minor mode > whose value is t, but that does not work. The people will start > complaining that the package does not work. > > I have seen this happen. Is there any reason not to handle the problem > the way I suggested? It looks like when custom-set-variables is written out the load dependency is not part of it. Is there anything else besides that?