From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Abrahams Subject: Re: Bug: org-install must precede customization [7.02trans] Date: Sun, 14 Nov 2010 08:29:26 -0500 Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from [140.186.70.92] (port=48550 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PHceG-0003rT-B1 for emacs-orgmode@gnu.org; Sun, 14 Nov 2010 08:29:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PHceC-0005nn-7Z for emacs-orgmode@gnu.org; Sun, 14 Nov 2010 08:29:36 -0500 Received: from mail-qy0-f169.google.com ([209.85.216.169]:61115) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PHceB-0005nd-Tm for emacs-orgmode@gnu.org; Sun, 14 Nov 2010 08:29:32 -0500 Received: by qyk1 with SMTP id 1so1486227qyk.0 for ; Sun, 14 Nov 2010 05:29:31 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Anupam Sengupta Cc: John Wiegley , emacs-orgmode@gnu.org, Carsten Dominik At Sat, 13 Nov 2010 11:25:25 +0530, Anupam Sengupta wrote: > > >>>>> David Abrahams writes: > > > Is it merely the autoload of org-capture-templates, or is this a > > general rule for everything in org-install? I think I'm perfectly > > happy to work with the dependency in place as long as it's > > documented. For most people it wouldn't be an issue since > > custom-* puts its custom-set-variables call at the end of the > > file. I think you need to be using something like initsplit to > > see the problem. > > The problem also comes up when a separate file is used for storing > the `custom-set-variables', i.e., something like: > > (setq custom-file "~/emacs-custom.el") > (load custom-file) > > Because of the autoload, these statements now need to be at the very > end of the init.el file. Not a big problem, but still something > that needs to be known (and was not required prior to 7.02). Yes, that --- in part --- is how I noticed this problem. -- Dave Abrahams BoostPro Computing http://www.boostpro.com