From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: guile-user@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Sun, 17 May 2020 12:36:36 -0400 [thread overview]
Message-ID: <871rniseln.fsf@dustycloud.org> (raw)
In-Reply-To: <CAJ98PDwtTQnqvLVSdj5TuRUFrwpO3vNVMtp4Mr15hYCuxbZaXg@mail.gmail.com>
Catonano writes:
> Now, I like to remind that Ludo had proposed to _mention_ guile-hall in the
> guix.texi manual !!
>
> Here:
> https://lists.gnu.org/archive/html/guile-user/2018-07/msg00002.html
>
> "I think we should advertise it widely"
>
> I wholeheartedly agree
>
> This is an important step in making the Guile user experience less rough
>
> Where, in the manual, should such mention be placed ?
The comparative frustration I had with having to use autotools for
simple guile projects vs when I was developing in Racket was one of the
things that came up in my FOSDEM talk last year. I didn't know that in
my absence Guile Hall came to be, though people told me later.
I'm excited that Guile Hall has reduced this overhead considerably, so I
agree with all the above. That's all to say, thank you Alex for working
on one of the most important problems in Guile! This is great!
next prev parent reply other threads:[~2020-05-17 16:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 15:41 [ANN] Guile Hall 0.3.0 released Alex Sassmannshausen
2020-05-16 16:14 ` Jack Hill
2020-05-16 16:22 ` Catonano
2020-05-16 20:57 ` Alex Sassmannshausen
2020-05-17 5:13 ` Catonano
2020-05-17 15:35 ` Alex Sassmannshausen
2020-05-17 17:37 ` Catonano
2020-05-17 18:31 ` Arne Babenhauserheide
2020-05-17 20:55 ` Alex Sassmannshausen
2020-05-18 5:43 ` Arne Babenhauserheide
2020-05-17 20:48 ` Alex Sassmannshausen
2020-05-18 16:19 ` Catonano
2020-05-20 11:45 ` Catonano
2020-05-20 11:46 ` Alex Sassmannshausen
2020-05-20 15:58 ` Catonano
2020-05-21 10:00 ` Catonano
2020-05-21 10:03 ` Alex Sassmannshausen
2020-05-22 5:16 ` Catonano
2020-05-24 21:22 ` Alex Sassmannshausen
2020-05-25 6:31 ` Catonano
2020-05-25 7:13 ` Alex Sassmannshausen
2020-05-25 7:51 ` Catonano
2020-05-26 14:37 ` Catonano
2020-05-27 20:52 ` Ludovic Courtès
2020-05-28 5:01 ` Catonano
2020-05-28 12:32 ` Ludovic Courtès
2020-05-28 12:35 ` Catonano
2020-05-28 15:54 ` Ludovic Courtès
2020-05-28 17:26 ` Catonano
2020-05-29 8:27 ` Ludovic Courtès
2020-05-29 9:09 ` Catonano
2020-05-29 10:52 ` Alex Sassmannshausen
2020-05-17 16:36 ` Christopher Lemmer Webber [this message]
2020-05-17 20:40 ` Alex Sassmannshausen
2020-05-17 20:21 ` Jérémy Korwin-Zmijowski
2020-05-18 15:43 ` 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=871rniseln.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).