From: Taiju HIGASHI <higashi@taiju.info>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Support for guile-config 0.5
Date: Thu, 02 Jun 2022 09:52:17 +0900 [thread overview]
Message-ID: <87czfrevjy.fsf@taiju.info> (raw)
In-Reply-To: <871qw8yvi3.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 01 Jun 2022 22:29:28 +0200")
Hi Ricardo,
> I’ll play with this some more and try to come up with better input
> validation.
Thank you!
By the way, GWL is a very interesting tool for me.
I had never seen such effective use of Wisp (or variants of
M-expression) as GWL.
I thought it was an attractive feature when using Wisp as a DSL.
I often write CI and other automated scripts, so I would love to try it
if I get the chance!
Cheers,
--
taiju
next prev parent reply other threads:[~2022-06-02 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 3:31 Support for guile-config 0.5 Taiju HIGASHI
2022-06-01 13:01 ` Ricardo Wurmus
2022-06-01 14:28 ` Taiju HIGASHI
2022-06-01 20:29 ` Ricardo Wurmus
2022-06-02 0:52 ` Taiju HIGASHI [this message]
2022-06-06 11:23 ` Ricardo Wurmus
2022-06-06 15:25 ` Taiju HIGASHI
2022-07-06 8:36 ` Ricardo Wurmus
2022-07-06 9:54 ` Taiju HIGASHI
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.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czfrevjy.fsf@taiju.info \
--to=higashi@taiju.info \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.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).