From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>,
Arne Babenhauserheide <arne_bab@web.de>,
guile-devel <guile-devel@gnu.org>
Subject: Re: Wisp as shipped language in Guile?
Date: Tue, 19 Sep 2017 09:10:08 -0500 [thread overview]
Message-ID: <87lgla7pa7.fsf@dustycloud.org> (raw)
In-Reply-To: <D1B05BDB-A70B-4F78-89D7-C52AE2976C1F@gmail.com>
Matt Wette writes:
>> On Sep 17, 2017, at 4:22 PM, Arne Babenhauserheide <arne_bab@web.de> wrote:
>>
>>
>> Matt Wette <matt.wette@gmail.com> writes:
>>> Looks promising, especailly if the footprint is small.
>>> Can someone post the sample guix specification?
>>> I could not access from the gnunet log.
>>
>> Do you mean the wisp package for Guix?
>
> No, I meant the guix package spec for package foo written in wisp.
>
> define-public foo
> package
> name "guile-wisp"
> source : origin
> ...
https://dustycloud.org/blog/wisp-lisp-alternative/
next prev parent reply other threads:[~2017-09-19 14:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 20:56 Wisp as shipped language in Guile? Arne Babenhauserheide
2017-05-08 2:34 ` Christopher Allan Webber
2017-05-13 1:52 ` Mark H Weaver
2017-05-13 7:24 ` Panicz Maciej Godek
2017-05-13 9:44 ` Arne Babenhauserheide
2017-05-16 19:27 ` nice option to have Fox
2017-05-18 23:03 ` Wisp as shipped language in Guile? Arne Babenhauserheide
2017-05-19 14:54 ` Wisp for Racket / Dr.Racket ? Fox
2017-05-19 21:06 ` more extensible reader directive, was: Wisp as shipped language in Guile? Arne Babenhauserheide
2017-08-11 9:04 ` Arne Babenhauserheide
2017-08-11 17:28 ` Nala Ginrut
2017-09-17 19:10 ` Arne Babenhauserheide
2017-09-17 20:28 ` Matt Wette
2017-09-17 23:22 ` Arne Babenhauserheide
2017-09-18 0:24 ` Matt Wette
2017-09-18 19:21 ` Arne Babenhauserheide
2017-09-19 14:10 ` Christopher Allan Webber [this message]
2017-09-19 23:46 ` Nala Ginrut
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgla7pa7.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=matt.wette@gmail.com \
--cc=mhw@netris.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).