RE: [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA

[Drew Adams <drew.adams@oracle.com>]

> > > > The "implicitly defined order" would be explicitly
> > > > defined (doc'd).  And it would only be the default.
> > >
> > > We seem to have different notions of explicit :-)
> 
> > As mentioned, you can explicitly load `custom-file'
> > from your init file.
> 
> We are still mis-communicating. If `custom-file'
> isn't loaded explicitly from the init file, what
> you propose is that it's loaded implicitly anyway.

Only under particular circumstances.

1. `custom-file' is nil by default.  Loading
   that is a no-op.

2. You can set `custom-file' to your init file.
   No change from current behavior, once you've
   done that.  End of story.

3. No automatic loading of `custom-file' if
   it's already been loaded.

4. You'll be able to set a variable, to prevent
   any automatic loading of `custom-file'.

IF you define a `custom-file' different from
your init file, and IF you use Customize, to
fill that file, and IF you don't load it from
your init file, and IF you don't set the var
to prevent it from being loaded automatically,
THEN it'll be loaded just after your init file.

And this will be documented.

> *That*'s what I perceive as "Magic".

Not what I'd call hidden magic.  But magic's
in the eye of its believer.