Re: custom.el shadow

>>>>> "Neal" == Neal D Becker <nbecker(a)hns.com&gt; writes: jpw> lisp/custom.el is dumped, so (require 'custom) should be a jpw> no-op Stephen> Correct. You can't require the personal custom.el (without using the Stephen> explicit path argument, and it will fail because custom.el normally Stephen> does not do (and should not do) a provide). jpw> (infact it shadows ~/.xemacs/custom.el; if ~/.xemacs/ jpw> shouldn't be in `load-path' then whatever abritrary thing jpw> puts it there may stick it ahead of lisp/) Stephen> I'm not sure about this. Mike? Michael> John is right: ~/.xemacs isn't normally in load-path, and isn't Michael> supposed to be. Neal needs to figure out where that comes from. Neal> Yes, ~/.xemacs is on my load-path. It seemed to me that if I was Neal> already putting emacs init files there, why not put my other elisp Neal> files there also? Michael> Because there are already package hierarchies under ~/.xemacs in your Michael> load-path for your convenience. You're simply using the system in a Michael> way it was not intended to be used. Like Neal, I also have ~/.xemacs. I think this comes from long ago when there weren't such things as package hiearchies. At least I'm pretty sure I had .xemacs in my load-path before packages existed. Oh well. I guess I should delete that now, now that there are package hierarchies and I'm actually using them. Ray