From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: guile-user@gnu.org
Subject: Re: Guile Hacker Handbook - Character sets
Date: Thu, 18 Feb 2021 22:56:55 +0100 [thread overview]
Message-ID: <44b041e7-6969-e6d2-8683-0fa47d080bc4@posteo.de> (raw)
In-Reply-To: <B9B5B608-F033-4FF6-BFDA-A04EDF8FB87B@korwin-zmijowski.fr>
Hello Jeremy!
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. : )
There is guile-studio as well:
https://guix.gnu.org/en/packages/guile-studio-0.1.0-1.93622e7/ (That's
what I found on a quick guix search.), which is already making use of
Emacs, as far as I remember. I think someone on the guile IRC channel
mentioned it and might be here on the mailing list. Perhaps the goals of
that project are different from guile-ide, but I thought I should
probably mention it.
Best regards,
Zelphir
On 2/18/21 8:54 PM, Jérémy Korwin-Zmijowski wrote:
> Dear Guilers !
>
> I happily managed to find some time to write a new chapter for the Guile Hacker Handbook !
>
> https://jeko.frama.io/en/char-sets.html
>
> It deals with char-sets, something new to me. The exercise was fun, I liked how convenient it is to play with these data type.
>
> As always, I would be glad to start a conversation around my code snippets, the handbook, test driven development, or whatever linked to Guile ! :-)
>
> The next chapter will probably introduce macros (syntax-rules) !
>
> For those who missed it, I am also starting a work towards a guile-ide.el for Emacs.
>
> https://framagit.org/Jeko/guile-ide
>
> Actually it's just a set of extensions I use (or will) and some feature I would like it to provide. I plan to engage with the Emacs team to see how we can work together to enhance the Guile hacking experience !
>
> Thank you !
> Cheers !
>
> Jérémy
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2021-02-18 21:56 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 [this message]
2021-02-19 11:23 ` Jérémy Korwin-Zmijowski
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=44b041e7-6969-e6d2-8683-0fa47d080bc4@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
/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).