From: Carsten Dominik <carsten.dominik@gmail.com>
To: Anupam Sengupta <anupamsg@gmail.com>
Cc: David Abrahams <dave@boostpro.com>,
emacs-orgmode@gnu.org, John Wiegley <johnw@boostpro.com>
Subject: Re: Bug: org-install must precede customization [7.02trans]
Date: Sat, 13 Nov 2010 00:00:06 -0600 [thread overview]
Message-ID: <CBBF643F-2491-4D1B-8650-FA3F6AA8DA1A@gmail.com> (raw)
In-Reply-To: <m239r5py2a.fsf@gmail.com>
On Nov 12, 2010, at 11:55 PM, Anupam Sengupta wrote:
>>>>>> David Abrahams <dave@boostpro.com> 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).
It is no longer required now. Removing the autoload cookie fixes the
problem. But you need to re-create org-install.el by running make.
- Carsten
next prev parent reply other threads:[~2010-11-13 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 18:45 Bug: org-install must precede customization [7.02trans] David Abrahams
2010-11-12 22:29 ` Carsten Dominik
2010-11-13 3:28 ` David Abrahams
2010-11-13 4:40 ` Carsten Dominik
2010-11-13 5:01 ` David Abrahams
2010-11-13 5:50 ` Carsten Dominik
2010-11-14 13:28 ` David Abrahams
2010-11-13 5:55 ` Anupam Sengupta
2010-11-13 6:00 ` Carsten Dominik [this message]
2010-11-14 13:29 ` David Abrahams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CBBF643F-2491-4D1B-8650-FA3F6AA8DA1A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=anupamsg@gmail.com \
--cc=dave@boostpro.com \
--cc=emacs-orgmode@gnu.org \
--cc=johnw@boostpro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).