From: Chris Marusich <cmmarusich@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Article: Playing with Guix REPL from scratch
Date: Wed, 09 Jan 2019 23:46:42 -0800 [thread overview]
Message-ID: <87y37tj6ot.fsf@gmail.com> (raw)
In-Reply-To: 88236E68-9FB3-4CE1-B8CE-9D1D60828D1B@pretty.Easy.privacy
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Hi,
Nice article! I love seeing how other people hack around on stuff. It
opens one's mind up to new perspectives and techniques.
FYI, there is an email list specifically for blog post review:
guix-blog@gnu.org. I'm not sure if it's still active, since I can't
find an entry for it on lists.gnu.org. In the future (assuming it's
still active), you can send your blog post there specifically for
review.
I've used the Guile REPL, but I haven't used the "Guix REPL". Is it
equivalent to firing up a Guile REPL and importing a bunch of modules,
or does it provide more features than you can get using just the Guile
REPL?
I can probably answer that question myself by browsing the docs and
looking at the source code, but for a blog post, it might be worth
taking a paragraph to explain how it is similar, and how it is
different, from the usual Guile REPL. In particular, what does it offer
that I can't get via a usual Guile REPL?
Thank you for sharing the article!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-01-10 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 11:47 Article: Playing with Guix REPL from scratch swedebugia
2018-12-25 18:01 ` swedebugia
2019-01-05 17:37 ` Ludovic Courtès
2019-01-06 3:24 ` swedebugia
2019-01-06 11:36 ` Pierre Neidhardt
2019-01-08 16:25 ` Ludovic Courtès
2019-01-10 7:46 ` Chris Marusich [this message]
2019-01-13 21:52 ` Ludovic Courtès
2019-01-14 9:44 ` Chris Marusich
2019-01-15 22:32 ` Ludovic Courtès
2019-01-23 1:52 ` Chris Marusich
2019-01-23 11:11 ` Ludovic Courtès
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=87y37tj6ot.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=swedebugia@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).