>>>> "David" == David A Cobb
<superbiskit(a)home.com> writes:
David> Following a recent discussion here, I have "(load
David> "~/custom.el") at the top of init.el. Would that
David> accomplish the same?
Partially. However, unless you rename custom.el, custom.el will be
reloaded after init.el. This is a problem in two cases:
(1) init.el recomputes values for customized variables.
(2) init.el adds specifications to faces.
In both cases reloading custom.el will smash the changes made by init.el.
If you do rename custom.el, setq custom-file to the new name in
init.el. This tells Custom where to store new settings. (Otherwise
it will recreate custom.el.)
David> Would it cause other problems?
This means that any code you have in init.el can depend on
Customizations. This is unanimously agreed to be a good thing in
general.
Of course, this is Lisp, _anything_ can cause problems. If you forget
that init.el depends on Customized variables (or Customize a variable
that you forgot is used by init.el) you could get unexpected behavior.
I believe it is always possible to get the default value of Customized
variables (this is not true of specifiers, eg, faces), so a properly
written init.el could be mostly free of such side effects of Custom.
On the other hand, I know of no mechanism for Custom to take advantage
of settings in init.el. So we are currently considering changing the
loading order. This would mean your custom.el would get loaded twice,
but I believe that is idempotent.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."