From: Vijay Marupudi <firstname.lastname@example.org>
To: Catonano <email@example.com>, guile-devel <firstname.lastname@example.org>
Subject: Re: a cookbook
Date: Mon, 14 Feb 2022 12:01:33 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
> Is there any interest/possibility to have such a cookbook hosted
> within the Guile official documentation (as it is for Guix) ?
I personally think that a Cookbook should be an independent effort, with
links from the Guile Manual if possible. This would lighten the load on
the maintainers, and allow for quicker collaboration.
To start, I think people should write Guile tutorials about things they
know about, license them using an open license, and let the community
know about the tutorials. Compiling these tutorials into a Cookbook
should be easy then.
Many tutorials exist out there, they need to found and listed. For e.g.,
here is a very detailed tutorial by Erik Edrosa on how to setup an Guile
Or snippets to capture stdout and stderr from a process from Arne
Finding and compiling lists of existing tutorials and snippets would be
a productive way to start on this effort.
I've personally started on this effort yesterday, writing about error
handling in Guile.
I'd be happy to create a website compiling everything together, but the
hard part is writing and finding the tutorials.
next prev parent reply other threads:[~2022-02-14 17:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 6:44 a cookbook Catonano
2022-02-14 15:47 ` Max Brieiev
2022-02-14 16:56 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-02-16 7:12 ` Catonano
2022-02-14 17:01 ` Vijay Marupudi [this message]
2022-02-16 7:21 ` Catonano
2022-02-16 9:54 ` Neil Jerram
2022-02-16 21:13 ` Catonano
2022-02-19 13:18 ` Neil Jerram
2022-02-20 11:07 ` Catonano
2022-02-16 14:19 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-02-17 2:11 ` Vijay Marupudi
2022-02-17 7:00 ` Catonano
2022-02-17 17:34 ` Vijay Marupudi
2022-02-14 22:00 dsmich
2022-02-14 23:06 ` Vijay Marupudi
2022-02-18 14:32 dsmich
2022-02-20 0:48 ` Vijay Marupudi
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:
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 \
* 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).