Richard Stallman <rms@gnu.org> writes:

My recommendation based on some of the present drawbacks I enumerated
might be to split the custom file into per-package customizations plus
an emacs-core piece. That might leave too many small files though which
is the other end of the pendulum's swing with respect to the
windows-registry single file failure, ie the UNIX world of a zillion
dot-files  --- but given the experience of both worlds, perhaps we can
find a good middle ground.> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > For separating customizations into multiple files there is "initsplit"
>   > (https://www.emacswiki.org/emacs/InitSplit). Maybe it's possible to
>   > include its functionality as part of Custom.
>
> I am sure we can implement the basic idea.  What I wonder about is,
> how to split the settings up?  Based on what sort of plan or system?
>
> If we have a clear answer for that, it should be a straightforward
> matter of doing work.

-- 
♈ Id: kg:/m/0285kf1  🦮