Re: custom.el shadow

Michael> Because there are already package hierarchies under Michael> ~/.xemacs in your load-path for your convenience. You're Michael> simply using the system in a way it was not intended to Michael> be used. Pointer to documentation? I suspect that this is yet another aspect of the new init system that is very clear to you, but counter- intuitive to many users. It seems obvious to me that people are going to put personal stuff in ~/.xemacs as it gets split out from init.el (eg, I do this a lot), and then many will put ~/.xemacs on their load-path (I happen not to do this, because I move such stuff into packages relatively quickly). Ray> Like Neal, I also have ~/.xemacs. I think this comes from Ray> long ago when there weren't such things as package Ray> hiearchies. At least I'm pretty sure I had .xemacs in my Ray> load-path before packages existed. Ray> Oh well. I guess I should delete that now, now that there Ray> are package hierarchies and I'm actually using them. Please do. The Emacs initialization process had become impossibly baroque and non-deterministic. Michael's cleanup is a GoodThang: it makes initialization predictable, much more automatic, and faster (due to optimizing away a large number of unnecessary calls to stat(2)). -- 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