Re: custom.el shadow

Mike, do you have any comments? Ray> Uhh, wait. What am I volunteering to delete here? :-) I Ray> guess that was ~/.xemacs from my load-path. Ray> Then where am I supposed to put my own stuff like my Ray> personalized versions and modifications of existing stuff? ~/.xemacs/xemacs-packages/lisp/ray-stuff/ Baroque, I know, but initialization will pick that up automatically and stick it in load-path. If you have an auto-autoloads file there, it will pick it up automatically: xemacs -batch -vanilla -l autoload -f batch-update-directory \ ~/.xemacs/xemacs-packages/lisp/ray-stuff should create it for you (of course, you have to put the appropriate autoload cookies in the files). Note that autoloads will possibly get you in trouble if you have a personalized version of a library available elsewhere on load-path. In that case just require it in init.el; the stuff in ~/.xemacs comes very early in load-path. To make sure you're getting what you expect, check for the ~/.xemacs elements of load-path, and use M-x list-load-path-shadows to make sure that any shadows are picking up the versions you want. (Usually that will be your personalized version.) -- 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