From: Vivien <vivien@planete-kraus.eu>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>,
"Olivier Dion" <olivier.dion@polymtl.ca>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Newbie thoughts on Guile Hall + Guix
Date: Thu, 10 Feb 2022 19:03:01 +0100 [thread overview]
Message-ID: <23c4e6ff67c11ecd62cf625b990b6389297935b4.camel@planete-kraus.eu> (raw)
In-Reply-To: <CA+XASoUz5rU4nr6474jW++NcJCgYWCeROP5p+vXwoF0kDJwwXQ@mail.gmail.com>
Hello,
Le mercredi 09 février 2022 à 12:05 -0800, Aleix Conchillo Flaqué a
écrit :
> - The manual is written by very smart people for very smart people.
> Not for
> newcomers.
To be more precise, I had that feeling everywhere I stumbled on the
word "continuation" : it took me days or weeks to understand dynamic
wind, handling exceptions, and prompts. The continuation concept
doesn’t exist in popular programming languages, so it’s hard to make
one of these quick hands-on guide "You did this in python, do that in
guile". I’m not sure there’s an easy solution though.
Vivien
next prev parent reply other threads:[~2022-02-10 18:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:30 Newbie thoughts on Guile Hall + Guix Blake Shaw
2022-02-09 14:13 ` Olivier Dion via General Guile related discussions
2022-02-09 20:05 ` Aleix Conchillo Flaqué
2022-02-09 20:28 ` Maxime Devos
2022-02-09 21:13 ` Aleix Conchillo Flaqué
2022-02-10 18:03 ` Vivien [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 12:42 Blake Shaw
2022-02-09 3:23 Blake Shaw
2022-02-08 16:13 Blake Shaw
2022-02-08 12:19 Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09 6:28 ` Catonano
2022-02-06 13:40 dsmich
2022-02-05 20:01 Christine Lemmer-Webber
2022-02-05 22:15 ` Mikael Djurfeldt
2022-02-05 23:19 ` Jose Antonio Ortega Ruiz
2022-02-06 14:09 ` Ricardo Wurmus
2022-02-06 0:40 ` Christine Lemmer-Webber
2022-02-06 4:54 ` Aleix Conchillo Flaqué
2022-02-06 13:14 ` Mikael Djurfeldt
2022-02-06 14:03 ` Ricardo Wurmus
2022-02-06 14:28 ` Vijay Marupudi
2022-02-06 14:53 ` Ognen Duzlevski
2022-02-06 15:13 ` Maxime Devos
2022-02-06 15:29 ` Vijay Marupudi
2022-02-06 21:34 ` Zelphir Kaltstahl
2022-02-07 2:11 ` David Pirotte
2022-02-07 2:47 ` David Pirotte
2022-02-07 19:21 ` Zelphir Kaltstahl
2022-02-07 22:35 ` adriano
2022-02-05 22:16 ` Vivien
2022-02-06 2:53 ` Zelphir Kaltstahl
2022-02-06 16:35 ` Olivier Dion via General Guile related discussions
2022-02-06 16:44 ` Vivien Kraus
2022-02-06 22:10 ` Olivier Dion via General Guile related discussions
2022-02-06 16:55 ` Maxime Devos
2022-02-06 22:05 ` Olivier Dion via General Guile related discussions
2022-02-06 22:32 ` Maxime Devos
2022-02-06 23:00 ` Olivier Dion via General Guile related discussions
2022-02-06 21:37 ` Zelphir Kaltstahl
2022-02-06 22:12 ` Olivier Dion via General Guile related discussions
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=23c4e6ff67c11ecd62cf625b990b6389297935b4.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--cc=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).