unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Leo Butler <leo.butler@umanitoba.ca>
To: guile-user@gnu.org
Subject: Re: "Missing" libraries/concepts found in other languages/ecosystems?
Date: Thu, 09 Jul 2020 13:12:27 -0500	[thread overview]
Message-ID: <86lfjswoac.fsf@x201.butler.org> (raw)
In-Reply-To: <d50e6d0f-686a-e02a-ba03-d1998d012a4d@gmail.com> (Zelphir Kaltstahl's message of "Wed, 8 Jul 2020 20:22:17 +0200")

Zelphir Kaltstahl <zelphirkaltstahl@gmail.com> writes:

<snip>

> To what others already have written I will add:
>
> From time to time one can copy ideas from Racket or look at what exists
> in Racket for solving a problem or seeing what the approach is.
>
> Catonano identified already the lack of examples in the Guile guide. I
> fight with that myself, so I created a repository with examples. Perhaps
> I should somehow add them to the guide. I've not looked into how to do
> that. Probably some commit in a repo somewhere for the guide:
>
> https://notabug.org/ZelphirKaltstahl/guile-examples
>
> Hope this can help!

Oh yes, thank you. That repository is a gem.

(I think it wouldn't take too much work to transform the repo as is into
a texinfo document on its own.)

---

The guile guide has been knocked. I agree that it could use more
examples, but I have found it is well-written and accurate.

Leo



  reply	other threads:[~2020-07-09 18:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.75.1594224014.21222.guile-user@gnu.org>
2020-07-08 18:22 ` "Missing" libraries/concepts found in other languages/ecosystems? Zelphir Kaltstahl
2020-07-09 18:12   ` Leo Butler [this message]
2020-07-09 19:34     ` Zelphir Kaltstahl
2020-07-10  7:39   ` Aleix Conchillo Flaqué
2020-07-10  8:14     ` Alex Sassmannshausen
2020-07-10  8:49   ` Catonano
2020-07-10 10:21     ` Chris Vine
2020-07-10 11:20       ` Catonano
2020-07-11  0:19         ` Zelphir Kaltstahl
2020-07-11  0:34           ` Zelphir Kaltstahl
2020-07-11 10:14             ` Chris Vine
2020-07-11 13:45               ` Stefan Israelsson Tampe
2020-07-11 14:46             ` Linus Björnstam
2020-07-11 10:13           ` Chris Vine
2020-07-11 18:20             ` John Cowan
2020-07-11 22:39               ` Chris Vine
2020-07-11 22:41                 ` John Cowan
2020-07-11 23:09                   ` Chris Vine
2020-07-12  1:52                     ` John Cowan
2020-07-12 20:26                       ` Chris Vine
2020-07-13 10:10                 ` Chris Vine
2020-07-12 16:08             ` Catonano
2020-07-12 16:10               ` Catonano
2020-07-12 17:46               ` John Cowan
2020-07-12 19:14               ` Chris Vine
2020-07-12 19:32                 ` Chris Vine
2020-07-14 10:32                   ` Catonano
2020-07-14 11:06                     ` Catonano
2020-07-14 16:21                     ` Chris Vine
2020-07-12 20:33               ` Zelphir Kaltstahl
2020-07-08  7:38 Simen Endsjø
2020-07-08  8:15 ` Vladimir Zhbanov
2020-07-08 10:08 ` Catonano
2020-07-08 11:29 ` Chris Vine
2020-07-10 12:15 ` Christopher Lam
2020-07-10 15:52   ` Chris Vine

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=86lfjswoac.fsf@x201.butler.org \
    --to=leo.butler@umanitoba.ca \
    --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).