From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: guile-user@gnu.org
Subject: Re: Guile cookbook ?
Date: Sat, 12 Feb 2022 17:11:46 +0000 [thread overview]
Message-ID: <a7775278-956d-64cd-67f8-77ab4a4dd61d@posteo.de> (raw)
In-Reply-To: <db2ea3e52abf98c0ac12448ead500030b52b65eb.camel@riseup.net>
On 2/12/22 15:01, adriano wrote:
> Il giorno sab, 12/02/2022 alle 14.55 +0100, adriano ha scritto:
>> Hint taken :-)
> Actually, I was thinking about a Guile cookbook, rather than the Guix
> cookbook
>
> Can the Guix cookbook also contain examples of how o do things in Guile
> ?
>
> Even things that are no related to Guix ?
Hi Adriano and everyone,
some more time examples:https://notabug.org/ZelphirKaltstahl/guile-examples/src/master/time Perhaps they can help.
If there is going to be a cookbook, feel free to copy examples and so on.
Best regards,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2022-02-12 17:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 8:37 timestamp adriano
2022-02-12 8:52 ` timestamp Vivien
2022-02-12 9:43 ` timestamp adriano
2022-02-12 11:49 ` timestamp Ricardo Wurmus
2022-02-12 12:32 ` timestamp tomas
2022-02-12 12:38 ` timestamp Eli Zaretskii
2022-02-12 13:30 ` timestamp adriano
2022-02-12 13:42 ` timestamp adriano
2022-02-12 13:49 ` timestamp Ricardo Wurmus
2022-02-12 13:55 ` timestamp adriano
2022-02-12 14:01 ` Guile cookbook ? adriano
2022-02-12 14:15 ` Ricardo Wurmus
2022-02-12 15:01 ` adriano
2022-02-12 15:30 ` Olivier Dion via General Guile related discussions
2022-02-12 17:11 ` Zelphir Kaltstahl [this message]
2022-02-12 17:32 ` timestamp Eli Zaretskii
2022-02-12 17:48 ` Examples in Guile documentation Zelphir Kaltstahl
2022-02-12 9:01 ` timestamp tomas
2022-02-12 9:49 ` timestamp adriano
2022-02-12 12:50 ` timestamp Eli Zaretskii
2022-02-12 13:01 ` timestamp tomas
2022-02-12 15:23 ` timestamp adriano
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=a7775278-956d-64cd-67f8-77ab4a4dd61d@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@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).