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

[Drew Adams]

> What would you do for users who already have 'custom-set-variables' in
> their init file?

Not a problem.  If they want `custom-file' to be
loaded at some explicit point, they do that in
the init file.  If they don't load it themselves
then - by default - it will be loaded after the
init file.  If they don't want it loaded
automatically at all, then they set a var that
prevents automatic loading.

> You'd have to arrange for custom-file *not* to
> be set for them, since otherwise subsequent
> saves of custom variables end up in the wrong file.

They would make any such arrangements themselves,
if they wanted.  Just set the var to never, ever,
load `custom-file'.

But what if they _want_ Customize changes to write
to their init file, and not to a `custom-file'
that they've configured to never get loaded?

(setq custom-file "/LOCATION/OF/MY/INIT-FILE")

> Iʼm not 100% sure you'd want it loaded after the init file either: how
> would you then do further changes that depend on the values set in
> your custom file?

Again, you control when, and even if, `custom-file'
gets loaded.  If you don't ever load it explicitly,
and if you don't set the variable to prevent it
from ever being loaded, then it's never loaded.