Re: custom-file

Hrvoje> Jan Vroonhof <vroonhof(a)math.ethz.ch&gt; writes: Hrvoje> It's not. My point is that I want to have a *choice* whether I want Hrvoje> `.xemacs/' or not, and for that choice to be respected. Well, having read the arguments for and against the creation of an .xemacs/ directory, I must say I am much more convinced by the arguments in favour. I believe that since we need several user files at startup (and even much more as soon as we have user installed packages) we should not clutter the home directory with a plethora of .xemacs-xxx files. Grouping things together under a single .xemacs/ directory is much cleaner and I am yet to see any good and objective reason for not doing so since until now I've only seen vain religious arguments. Of course, as usual, we should leave the option to the user to not use this scheme and have all his init/options/preferences/whatever files in the root directory... Sigh... Makes me think of a quite old professor here who never got used to using directories to put a little order in his files, instead he uses prefixes like a-xxx, a-yyy... Except for the unbelievable mess he now has in his home directory I could never see the difference with using a/xxx a/yyy... I currently have 98 hundred .* files (after deleting ~ files) in my home directory, I think it's enough of a mess not to have XEmacs add more... I believe that .xemacs/ should clearly be the default and multiple files in ~/ the option, not the opposite. Oscar