Re: custom.el shadow

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. Yes, ~/.xemacs is on my load-path. It seemed to me that if I was already putting emacs init files there, why not put my other elisp files there also? In my opinion, we should migrate towards names that don't clash, if at all possible.