From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Mailing list Guile User <guile-user@gnu.org>
Subject: Re: Blog post about Hall
Date: Thu, 11 Jun 2020 21:44:53 +0200 [thread overview]
Message-ID: <edb0f481d2704c822244f73f45df5471df8559ea.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <7dd74417-99a6-7c30-3102-855989d5fcec@posteo.de>
Hi Zelphir !
> So far I've not figured out how to use guile-hall and have been
> looking
> forward to some nice tutorial. This will come in handy!
If it does help you, it's worth writing !!!
Jérémy
next prev parent reply other threads:[~2020-06-11 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 15:10 Blog post about Hall Jérémy Korwin-Zmijowski
2020-06-11 16:22 ` divoplade
2020-06-11 16:44 ` Jérémy Korwin-Zmijowski
2020-06-11 17:13 ` Aleix Conchillo Flaqué
2020-06-11 19:30 ` Jérémy Korwin-Zmijowski
2020-06-11 20:07 ` Aleix Conchillo Flaqué
2020-06-11 18:22 ` Zelphir Kaltstahl
2020-06-11 19:44 ` Jérémy Korwin-Zmijowski [this message]
2020-06-12 20:32 ` 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://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=edb0f481d2704c822244f73f45df5471df8559ea.camel@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).