Re: .emacs vs .xemacs vs .xemacs.el vs...?
Hrvoje Niksic <hniksic(a)srce.hr> writes:
Rebecca Ore <rebecca.ore(a)op.net> writes:
> Right would be to have a .xemacs file,
That would be definitely wrong, if we ever plan to introduce a
`.xemacs/' directory. Confusing `.emacs' and `.xemacs/init.el' and
the various options is bad enough; if we add `.xemacs' as a *file*
into the picture, it's going to get *really* bad.
Then the right way would be:
1) Look if there is a .emacs and use it if it is found
2) Look for a directory .xemacs/ and if it is found
use init.el and options.el from this path
3) If nothing is found, create the .xemacs/ path and files (well, we are
XEmacs)
If case 2) or 3) is used, everything is fine, and the XEmacs config structure
can be used.
If the .emacs is found and used, than it must also put the customs into it,
cause thats the way the gnu guys do it (is this correct?).
Another possible way:
Always use .xemacs/*, and only use .emacs if argv[0] is 'emacs'!
Regards,
Oliver.