From: Catonano <catonano@gmail.com>
To: help-guix@gnu.org
Subject: working on guix: how to
Date: Sat, 4 Jun 2016 12:32:33 +0200 [thread overview]
Message-ID: <CAJ98PDxB-cYp-Qi7avsK=61j6e-XCkicWiVmhDfW1Uxg6y-Mkg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
Hello people
How do I hack on guix ?
I read about "guix environment guix" and that's ok
I also read that a special guile command can be thaught to Geiser so I
guess I could teach Geiser to use the Guile provided by "guix environment
guix". Right ?
But say I want to make a small modification on the actually running guix
and see the effect live.
How do I access the code of the guix running in the env provided by "guix
environment guix" ?
That is, how do I "incrementally" develop Guix ?
With "incrementally develop" I mean interactively testing snippets of code
and making small edits and then iterate
[-- Attachment #2: Type: text/html, Size: 851 bytes --]
next reply other threads:[~2016-06-04 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 10:32 Catonano [this message]
2016-06-04 11:22 ` working on guix: how to Matthew Jordan
2016-06-04 20:33 ` Ludovic Courtès
2016-06-06 10:48 ` Catonano
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='CAJ98PDxB-cYp-Qi7avsK=61j6e-XCkicWiVmhDfW1Uxg6y-Mkg@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=help-guix@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).