unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Jonathan Frederickson <jonathan@terracrypt.net>, help-guix@gnu.org
Subject: Re: Geiser and Guix - how to avoid long compilation steps?
Date: Tue, 26 May 2020 09:45:43 +0200	[thread overview]
Message-ID: <87o8qbm95k.fsf@ambrevar.xyz> (raw)
In-Reply-To: <1590447777.1469.0@terracrypt.net>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

Jonathan Frederickson <jonathan@terracrypt.net> writes:

> This despite the fact that I'm working on a copy of Guix that I've 
> already compiled with 'make' and that has the compiled copy alongside 
> the source.

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?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2020-05-26  7:46 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 [this message]
2020-05-26 21:19   ` Ludovic Courtès
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=87o8qbm95k.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=help-guix@gnu.org \
    --cc=jonathan@terracrypt.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.
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).