FWIW, ANSI Common Lisp does not *have* a current directory, only a
current value of `*default-pathname-defaults*`. ANSI CL is happy to run
on systems that have no notion of a process having a current directory.
So that accounts for why Quicklisp and ASDF don't support a notion of
current
Thank you all very much! It seems to me that changing QuickLisp to default to
the current directory first would solve all of the problems. This way one can
change to the application directory and all will load correctly without any
configuration.
Until that change is made, I will use one of
Right yeah, or you can use clpm and specifically target the versions of the
thing you use. Alternatively you can vendor (copy/paste them in your repo).
In CL you fo deal with per-platform thing, but generally it is isolated to
some OS layer and move on
On Sun, Sep 24, 2023 at 7:00 AM Attila
> I use a vanilla Quicklisp installation. For some local directory
> trees I configure ASDF to prefer those trees over the standard
> Quicklisp versions by placing text like the following in my
> $HOME/.config/common-lisp/source-registry.conf file:
>
> (:source-registry
> (:tree
