Re: custom.el shadow

kitty> How will having another version of the library available kitty> elsewhere affect autoload ? I thought that autoload means kitty> just that: automatically load the needed libraries by kitty> searching through load-path. It looks like that is true for the auto-autoloads we generate, but it needn't be. The autoload definition could specify an absolute path. But this isn't the real problem. kitty> Since ~/.xemacs/xemacs-packages/lisp/ should come much kitty> earlier than other paths, why would autoload not pick-up kitty> these versions and ignore the versions seen later in the kitty> load-path ? Most likely, it will. The problem is that auto-autoload files are _not_ limited to autoload definitions; they can have arbitrary code in them. They also provide features and check for them to prevent multiple loading. I don't see offhand how trouble would arise, but the situation is quite complicated. Best to be paranoid. -- 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