Re: *lib-directory* a relative path?!

[Sam S. <sd...@gn...>]

Hi Bruno,

On Fri, Dec 3, 2010 at 4:41 AM, Bruno Haible <br...@cl...> wrote:
> http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_load.html
> http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_compile-file.html

oops. I stand corrected.

> No. But when the user has set a directory in *default-pathname-defaults*
> he has to be prepared to seeing this directory being merged into all
> non-absolute pathnames he enters.
>
>> re: bug#3124200
>
> Haven't had time to look at that, sorry.

(setq *default-pathname-defaults* (cd)) breaks (require "rawsock")
because search-file now looks for "/home/...../rawsock" and not for
"rawsock".
since "rawsock" in require is a module designator, not a pathname
designator, I think that my first original patch replacing
merge-pathnames with pathname in search-file is actually correct.


-- 
Sam Steingold <http://sds.podval.org>