Re: user-init-directory set to "/.xemacs/" instead of "~/.xemacs/"
karlheg(a)cathcart.sysc.pdx.edu (Karl M. Hegbloom) writes:
It looks like `user-init-directory', as Stef points out, is
initialized to just "/.xemacs/", and is later used in combination
with `init-file-user' to form the filename path in
`load-user-init-file'. "package-get.el" just sets
`package-get-user-package-location' to `user-init-directory'.
Yes, my mistake.
This stuff needs to be gone over, I think.
`user-init-directory'
really ought to bear the `~' prefix; but the `init-file-user' thing
has to keep working.
Indeed. user-init-directory just needs to be constructed at run time.
It is confusing that user-init-directory isn't the full path, but
user-init-file is.
I'm a little angry that the `init.el' and `.options.el'
stuff got
backed out. Why was that done?
Because at the time of the feature freeze there were still some
problems with it and it was decided it needed more time to become
stable and thus it was postponed. With hindsight that was probably a
bad idea (we broke backwards compatibility anyway with the options
menu).
The main issue is not compatibility with FSF emacs. It is
compatibility with older XEmacsen. That is important and that is why
it is probably imperative to fall back on .emacs if that exists.
The other issue is proper migration of the customize stuff. I have
some ideas how to that.
email the author and it would be changed by the end of next week. I
will submit patches for this if they will be accepted.
If you want to see this feature in 21.2 (I want it too) it is better
to get it in as early as possible. However you need to give more
though to migration issues before it can go in.
Jan