From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Geiser and Guix - how to avoid long compilation steps?
Date: Tue, 26 May 2020 23:19:39 +0200 [thread overview]
Message-ID: <874ks2o0lw.fsf@gnu.org> (raw)
In-Reply-To: <87o8qbm95k.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Tue, 26 May 2020 09:45:43 +0200")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> This has been a source of headaches for me too. I like to run Geiser
> to hack my Guix checkout. But if I forget to compile a (big) scheme
> file, geiser will grind to a halt when switching to a module that
> depends on the uncompiled file.
>
> Something weird: If I repeat the module switch, Geiser still takes ages
> to do it, as if it didn't persist the .go files (normally in
> ~/.cache/guile/ccache?)
>
> In my understanding, the solution here is to run `guix environment
> guix -- make` all the time.
>
> Maybe I'll add an override for geiser-mode-switch-to-repl-and-enter that
> compiles Guix automatically.
>
> Any other tip?
I run “make” before starting the REPL to avoid the problem you mention
(bah!), but from there on I can happily hack on my stuff.
A little-known feature of Emacs-Guix is C-c . u (guix-devel-use-module),
which allows you to load a module without compiling it with C-c C-k.
It’s fast and non-intrusive, unlike C-c C-k.
Ludo’.
next prev parent reply other threads:[~2020-05-26 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 23:02 Geiser and Guix - how to avoid long compilation steps? Jonathan Frederickson
2020-05-26 0:05 ` divoplade
2020-05-26 2:32 ` Jonathan Frederickson
2020-05-26 6:18 ` divoplade
2020-05-26 7:45 ` Pierre Neidhardt
2020-05-26 21:19 ` Ludovic Courtès [this message]
2020-05-27 9:37 ` Pierre Neidhardt
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=874ks2o0lw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
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).