Re: Should XEmacs look for "./poe.el" on the load-path?

ms> `locate-file' has at least one other bug connected with ms> absolute file names. Unfortunately, there's quite a bit of ms> code which expects ms> (load-library "mule/foo.el") ms> to search the load-path. ms> So I suggest fixing ./ with locate-file, but leaving the other ms> case alone. I'll do it along with the other bug, if you guys ms> want me to. Stephen> What do you mean by "fixing"? I know what _I_ like, but treating Stephen> "./bar" as relative to `default-directory' but "foo/bar" as relative Stephen> to the path is pretty inconsistent. I personally don't think so. As this discussion showed, it depends on your intuition whether "." is absolute or relative. Stephen> It's pretty clear that my Stephen> intuition that "./bar" should be absolute is wrong as a Stephen> matter of Unix usage; there are specific references "relative Stephen> paths" that use "./bar" as an example in lread.c! Stephen> I think that the right way to "fix" this is to document it. :-( Stephen> What "other bug" are you talking about? Stephen> /* kludge: locate-file does not work for a null load-path, even if Stephen> the file name is absolute. */ This one: (locate-file "/usr/bin/ls" '()) nil -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla