Re: custom.el shadow

ms> ** New locations for early package hierarchies. On second thought, I see no conflict here with the package hierarchies. This would show up in a xemacs --no-packages, right? The problem is the shadowing of the name "custom.el", combined with users who think logically. Once it exists, ~/.xemacs is the obvious place for users to keep other dot files (.vm, .gnus, .sc, etc), personal libraries split out from init.el, and other third-party stuff they've collected. No? And once they've put stuff there, they'll probably put it on load-path, yes? If that is a bad thing as such, then we should document it and check for it. If it's only bad because of the shadowing of custom.el, we should change the default value of custom-file. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py