RE: always put Customizations in `custom-file', never in `user-init-file'

[Drew Adams]

> > `custom-file' would be loaded explicitly:
> > (load-file custom-file). Just as it is now. All I
> > proposed was that any Customize stuff currently in
> > `user-init-file' should be moved to `custom-file'.
>
> If custom-file is not loaded by default then it makes it even more
> difficult for users

Makes what more difficult for users? More difficult than what?

`custom-file' has never been loaded automatically. Why propose that? What
problem would that solve?

> so I think it have to be loaded by default.

Why?

When would you load it, wrt loading `user-init-file'? Before? After? In the
middle somewhere?

What would you do if the `user-init-file' or some file it loads has an
explicit (load-file `custom-file')? What if the automatic load had already
happened?

Users should be able to control when Customize customizations take place.
Loading `custom-file' automatically would reduce their control. That would
be a drastic, and negative, change from the current behavior.

> If something has to be done before custom-file I would prefer a separate
> file, .pre-custom-emacs or something. The only thing I believe would
> have to go there is actually the name of custom-file (if the user wants
> to change it).

That way lies madness...

How can you decide (for all users?) what "would have to go there" or when
`custom-file' should be loaded?

We need only two files: `user-init-file' and `custom-file'. The former
should be for users to edit (possibly to load other files). Editing the
latter should be discouraged: normally, users should not need to open
`custom-file' in an editor.