Re: questionable advice about Geiser load path setting

[wolf]

On 2023-09-04 21:41:44 -0400, Maxim Cournoyer wrote:
> Hello,
> 
> wolf <wolf@wolfsden.cz> writes:
> 
> [...]
> 
> > Geiser seems to add the project root (I assume based on the git) into the 
> > load
> > path automatically.  geiser-repl-current-project-function seems to be set by
> > default, and rest is described in the docs: (geiser)Customization and tips, 
> > Init
> > files and load paths.
> >
> > Maybe it once was necessary to set this, I am not sure it still is the case.
> >
> > I also use (setq geiser-repl-per-project-p t) and everything seems to just 
> > work
> > out of the box.
> 
> I haven't followed up with the latest Geiser features, but if what you
> wrote is true, then it would be nice to streamline our .dir-locals.el
> and simply set geiser-repl-per-project-p to t (as a directory-local
> variable).
> 
> Would you like to see if that continues working the same, across
> e.g. Git worktrees of Guix checkouts?

Seems to work as one would expect.  My Guix checkout is in /home/wolf/src/guix,
those in /tmp are worktrees.  I pressed C-c C-z in each of these files, a new
REPL was spawned for each of them.  After that I evaluated the snippet to verify
the paths.

/home/wolf/src/guix/gnu/packages/linux.scm:

    (values (car %load-path) (car %load-compiled-path))
    $8 = "/home/wolf/src/guix"
    $9 = "/home/wolf/src/guix"

/tmp/guix-a/gnu/packages/linux.scm:

    (values (car %load-path) (car %load-compiled-path))
    $5 = "/tmp/guix-a"
    $6 = "/tmp/guix-a"

/tmp/guix-b/gnu/packages/linux.scm:

    (values (car %load-path) (car %load-compiled-path))
    $5 = "/tmp/guix-b"
    $6 = "/tmp/guix-b"

C-c C-z in /tmp/guix-b/gnu/packages/abduco.scm reused the already running REPL
for the guix-b.

> 
> -- 
> Thanks,
> Maxim
>

W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

signature.asc
Description: PGP signature