Re: Autoloaded defcustoms

[Chetan Pandya <pandyacus@sbcglobal.net>]

--- On Tue, 1/6/09, Lennart Borgman <lennart.borgman@gmail.com> 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?