Re: find-function vs. Windows paths
On 30 May 2002, Stephen J. Turnbull wrote:
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.
I don't quite follow your description of the FAQ, but it would be cool
to have a variable that activates said load-path searching. It's not
really a prefix thing -- people like me, who install binary kits and the
sumo tarball, will *always* want to search the load-path when we use
find-function. So I'd like to set that behavior with a variable
and forget about it.
scott