Re: custom.el shadow

jpw> lisp/custom.el is dumped, so (require 'custom) should be a jpw> no-op Correct. You can't require the personal custom.el (without using the explicit path argument, and it will fail because custom.el normally 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/) I'm not sure about this. Mike? jpw> If `custom-file' is loaded like so: (load custom-file) or jpw> (load "/home/neal/.xemacs/custom.el") that should be fine. It's the former. That's why the custom-file variable exists. custom-file is initialized as (approximately) (expand-file-name "custom.el" (file-name-directory user-init-file)) It doesn't care about load-path. jpw> * I think 21.4's machinery for handling jpw> ~/.xemacs/{custom,init}.el differs from 21.5, right? No, not as far as this goes. I don't remember how far we've gone down the road to loading custom-file _before_ user-init-file (The RightThang[tm] and what we don't do yet in 21.4), but that's the only real difference that might be present here. -- 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