From: wolf <wolf@wolfsden.cz>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: brian <bjc@spork.org>, Csepp <raingloom@riseup.net>, guix-devel@gnu.org
Subject: Re: questionable advice about Geiser load path setting
Date: Tue, 5 Sep 2023 18:32:34 +0200 [thread overview]
Message-ID: <ZPdYImqCAJ1Ansm0@ws> (raw)
In-Reply-To: <871qfds8fb.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-05 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 4:03 questionable advice about Geiser load path setting Csepp
2023-08-26 11:27 ` brian via Development of GNU Guix and the GNU System distribution.
2023-08-31 19:10 ` wolf
2023-09-05 1:41 ` Maxim Cournoyer
2023-09-05 16:32 ` wolf [this message]
2023-09-06 18:46 ` Maxim Cournoyer
2023-08-27 1:42 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPdYImqCAJ1Ansm0@ws \
--to=wolf@wolfsden.cz \
--cc=bjc@spork.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=raingloom@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).