Re: find-function vs. Windows paths

Andy> Maybe Mike Sperber could comment on this. I've never Andy> understood why the compile time paths get put into the Andy> executable. Because those are the libraries that are loaded, of course. The intent was to make it easy for maintainers and hackers to find the libraries that need to be changed to fix bugs or enhance XEmacs. For them, load-history is the right place to look. If you don't have access to them, well, you don't have access to them. As it is, "It took me forever to find the damn library because find-library was looking for it in the wrong place, and now that I've found and fixed it XEmacs forgets all my changes when I restart" is a FAQ. If people would only build from source and run-in-place this wouldn't be a problem. ;-) One sensible way to handle this is to add a SEARCH-LOAD-PATH-TOO flag to `find-library' and `locate-library', if it's nil have them warn "library source not found, probably dumped into XEmacs? use prefix arg to search path" on not found, and if non-nil search for the library on the path. I would prefer those semantics (rather than defaulting to searching load-path) to reduce the incidence of the FAQ, but maybe I'm just a worry-wart. -- 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