From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: "Guile User" <guile-user@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Thu, 21 May 2020 12:03:17 +0200 [thread overview]
Message-ID: <bb95d6480c72c1ace9fb1cd01419b81a7aeab73d.camel@gmail.com> (raw)
In-Reply-To: <CAJ98PDzUcU2X1ErvPJuKm6uL-CjHP+G9WwFfSt-Tp+V+o0KtqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Heya,
On Thu, 2020-05-21 at 12:00 +0200, Catonano wrote:
>
>
> Il giorno mer 20 mag 2020 alle ore 17:58 Catonano <catonano@gmail.com
> > ha scritto:
> >
> > Ok this is the last revision for today
> > Now I'm gonna do something else, really ! 😀
> >
>
>
> So, today is another day and I have a new update
>
> I'm watching this talk
> https://peertube.social/videos/watch/8f27a614-aa63-4811-af6a-b9e11effc399
>
> and it made up my mind that in this patch I'm intermingling reference
> type content and tutorial type content
>
> Guile desperately lacks some good tutorial and how to materials
>
> Because, as the person on the video says, programmers tend to assume
> that what people want is information
>
> But the solution is not to spray the reference manual with bit of
> tutorials here and there
>
> Because, according to the person talking, that decreases the quality
> of both reference and tutorials
>
> Today I'm a bit busy but I'll submit a proper patch maybe tomorrow
I think these are very good points. I think that's where the
difference between the Guix Manual and the Cookbook come from.
The Guile manual is definitely a reference manual! :-)
I'll await your update tomorrow.
Alex
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2020-05-21 10:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 15:41 [ANN] Guile Hall 0.3.0 released Alex Sassmannshausen
2020-05-16 16:14 ` Jack Hill
2020-05-16 16:22 ` Catonano
2020-05-16 20:57 ` Alex Sassmannshausen
2020-05-17 5:13 ` Catonano
2020-05-17 15:35 ` Alex Sassmannshausen
2020-05-17 17:37 ` Catonano
2020-05-17 18:31 ` Arne Babenhauserheide
2020-05-17 20:55 ` Alex Sassmannshausen
2020-05-18 5:43 ` Arne Babenhauserheide
2020-05-17 20:48 ` Alex Sassmannshausen
2020-05-18 16:19 ` Catonano
2020-05-20 11:45 ` Catonano
2020-05-20 11:46 ` Alex Sassmannshausen
2020-05-20 15:58 ` Catonano
2020-05-21 10:00 ` Catonano
2020-05-21 10:03 ` Alex Sassmannshausen [this message]
2020-05-22 5:16 ` Catonano
2020-05-24 21:22 ` Alex Sassmannshausen
2020-05-25 6:31 ` Catonano
2020-05-25 7:13 ` Alex Sassmannshausen
2020-05-25 7:51 ` Catonano
2020-05-26 14:37 ` Catonano
2020-05-27 20:52 ` Ludovic Courtès
2020-05-28 5:01 ` Catonano
2020-05-28 12:32 ` Ludovic Courtès
2020-05-28 12:35 ` Catonano
2020-05-28 15:54 ` Ludovic Courtès
2020-05-28 17:26 ` Catonano
2020-05-29 8:27 ` Ludovic Courtès
2020-05-29 9:09 ` Catonano
2020-05-29 10:52 ` Alex Sassmannshausen
2020-05-17 16:36 ` Christopher Lemmer Webber
2020-05-17 20:40 ` Alex Sassmannshausen
2020-05-17 20:21 ` Jérémy Korwin-Zmijowski
2020-05-18 15:43 ` Nala Ginrut
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=bb95d6480c72c1ace9fb1cd01419b81a7aeab73d.camel@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).