Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
;; This depends on init-file-user through early-package-path
(setq custom-file (or (locate-library "options" nil
early-package-load-path ) custom-file))
I don't like this. early-package-load-path has a well-defined meaning
and is orthogonal to custom-file location. Linking them like this
looks like inviting trouble.
Also, your code would lose miserably with old `options.el', for
instance.
Backwards compatibility (with FSF and 20.4)
a. No ~.xemacs/lisp/init.el => .emacs is used.
b. If customize stuff is in .emacs that gets evalled (of course)
and custom stuff also saved there
Sensible, 'no suprise' defaults
c. ~/.emacs is still the default when init.el is not there.
[do we want that]
I wouldn't want ~/init.el to be evaluated, ever. Is it currently the
case?
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Beware of bugs in the above code; I have only proved it correct,
not tried it." -- Donald Knuth