From: jgart via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: lloda <lloda@sarc.name>
Cc: 57145@debbugs.gnu.org
Subject: bug#57145: [PATCH] Add xcons example
Date: Fri, 12 Aug 2022 08:15:50 -0500 [thread overview]
Message-ID: <20220812081550.GB24274@gac> (raw)
In-Reply-To: <A5353DDD-F395-4E01-A798-440A4FC9508D@sarc.name>
On Fri, 12 Aug 2022 09:48:13 +0200 lloda <lloda@sarc.name> wrote:
>
> Hi jgart,
>
> looks good, but could you do a patch for several of these at once?
Sure, give me a few weeks and I'll send a bigger patch with more.
Thanks for reviewing.
BTW, I don't think the xcons example I sent is a good one.
Do you happen to know how schemers would use it in the context of a hof?
The manual mentions that it would be useful in the context of a hof but doesn't show an example :(
all best,
jgart
https://whereis.みんな/
prev parent reply other threads:[~2022-08-12 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 22:03 bug#57145: [PATCH] Add xcons example jgart via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2022-08-12 7:48 ` lloda
2022-08-12 13:15 ` jgart via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
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=20220812081550.GB24274@gac \
--to=bug-guile@gnu.org \
--cc=57145@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lloda@sarc.name \
/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).