sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
Jan> Hrvoje Niksic <hniksic(a)srce.hr> writes:
Jan> 3. We have .xemacs anyway for the package system.
3. is a reason *not* to use it for startup files. ~/.xemacs is a
package hierarchy. There's no lasting guarantee that its layout will
support putting random .el files in its root.
I don't understand what you mean. Could you clarify ?
In a long term, we could consider startup stuff as a virtual package,
belonging to .xemacs/lisp (say .xemacs/lisp/startup or init), in which we
would have at least a user file and a custom file. If one day we want another
file (like early.el), well it's easy to do. Many softwares have a .foobarrc/
startup and configuration directory. For us, it seems coherent to make it
behave as a package.
--
/ / _ _ Didier Verna
http://www.inf.enst.fr/~verna/
- / / - / / /_/ / E.N.S.T. INF C214 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72
75634 Paris cedex 13 Fax. (33) 01 45 81 31 19