unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: Guile Hacker Handbook - Character sets
Date: Fri, 19 Feb 2021 12:23:54 +0100	[thread overview]
Message-ID: <5570eb743f49067e4b1d816a4f4ff90dbd732816.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <44b041e7-6969-e6d2-8683-0fa47d080bc4@posteo.de>

Le jeudi 18 février 2021 à 22:56 +0100, Zelphir Kaltstahl a écrit :
> Hello Jeremy!

Hi Zelphir!

> I am looking forward to seeing a new chapter of your handbook,
> especially, if there is more stuff that explains macros and how to
> get
> something useful done with macros. : )

Thank you for your support. 
Macros are a wide topic, I will start with a syntax-rule to make use of
srfi-64 more attractive to me ! ;)

The "test-begin" "test-****" "test-end" feels too much procedural to me
haha

> There is guile-studio as well:
> https://guix.gnu.org/en/packages/guile-studio-0.1.0-1.93622e7/ 

I did read about it on the mailing list ! Hopefully we are
complementary. ;)

Jérémy




  reply	other threads:[~2021-02-19 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 19:54 Guile Hacker Handbook - Character sets Jérémy Korwin-Zmijowski
2021-02-18 21:53 ` Ricardo Wurmus
2021-02-19 11:15   ` Jérémy Korwin-Zmijowski
2021-02-18 21:54 ` Ricardo Wurmus
2021-02-19  8:10   ` Eli Zaretskii
2021-02-19 10:20     ` Jérémy Korwin-Zmijowski
2021-02-19 12:16       ` Eli Zaretskii
2021-02-18 21:56 ` Zelphir Kaltstahl
2021-02-19 11:23   ` Jérémy Korwin-Zmijowski [this message]
2021-02-19 17:26     ` Dr. Arne Babenhauserheide
2021-02-18 23:15 ` divoplade
2021-02-19  0:10   ` John Cowan
2021-02-19 12:59   ` Jérémy Korwin-Zmijowski
2021-02-19  7:09 ` Dr. Arne Babenhauserheide
2021-02-19 21:31   ` Jérémy Korwin-Zmijowski

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=5570eb743f49067e4b1d816a4f4ff90dbd732816.camel@korwin-zmijowski.fr \
    --to=jeremy@korwin-zmijowski.fr \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@posteo.de \
    /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).