Glynn Clements <glynn(a)sensei.co.uk> writes:
Hrvoje Niksic wrote:
> 3) Doing something about the old users' options in their `.emacs'
> files -- for instance, by moving them to the new file, or by
> ignoring multiple entries.[1]
How about binding custom-set-* (e.g. with flet) during the reading
of
user-init-file, to a function which displays a warning? This could
suggest that the user move these entries to the new file.
You can't tell which file it is being loaded from. If someone has
changed the value of custom-file and hand loads it in .emacs they will
now lose.
> 4) If `.xemacs/' is present, use it, otherwise choose a
default in
> home directory.
That's not very aggressive and provides a migration path. A
subdirectory particularly with the properties of the current .xemacs/
for package path searching (a feature I like *a lot* even though I
still use ~/.emacs instead of ~/.xemacs/init.el) is where we want
to end up.
As a general mechanism for this sort of thing, how about using
either
~/.xemacs/foo or ~/.xemacs-foo, depending upon whether ~/.xemacs/
exists?
That sounds good.