From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Geiser and Guix - how to avoid long compilation steps?
Date: Wed, 27 May 2020 11:37:14 +0200 [thread overview]
Message-ID: <877dwxg1md.fsf@ambrevar.xyz> (raw)
In-Reply-To: <874ks2o0lw.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> 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.
Thanks for the tip.
Although recently I've found Emacs-Guix increasingly unusable with many
features reporting errors
(e.g. package completion).
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-05-27 9:37 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
2020-05-27 9:37 ` Pierre Neidhardt [this message]
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=877dwxg1md.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/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).