From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: zimoun <zimon.toutoune@gmail.com>, Fulbert <fulbert@bluewin.ch>,
58463@debbugs.gnu.org
Subject: [bug#58463] [PATCH] * doc: guix-cookbook: Add a "Guix API usage examples"
Date: Thu, 20 Oct 2022 08:30:28 +0200 [thread overview]
Message-ID: <88c58e9fe09076e2ea7e29d1424c8f6e47c7d9a8.camel@ist.tugraz.at> (raw)
In-Reply-To: <864jw0p1ag.fsf@gmail.com>
Am Mittwoch, dem 19.10.2022 um 12:15 +0200 schrieb zimoun:
> Hi Liliana,
>
> On Tue, 18 Oct 2022 at 14:09, Liliana Marie Prikler
> <liliana.prikler@ist.tugraz.at> wrote:
>
> > I don't think it's useful to write out these timestamps in a way
> > that they're readable to the reader. They might be fine as
> > comments, but I'd also suggest diverging from simon's structure to
> > accomodate the switch in media (and possibly target audience?)
>
> What do you mean with
>
> I'd also suggest diverging from simon's structure to accomodate
> the switch in media (and possibly target audience?)
>
> ? The path “guix repl” -> script -> extension appears to me a nice
> journey. What would be your suggestion?
I don't have any problem with this part of the structure, the problem
arises when making a literal transcription of the slides. Revealing
information bit by bit and piecing things together slowly works great
in presentation where these bits of information can be augmented by
your speech and questions asked in between. In a manual (or cookbook)
however, it makes more sense to first show the complete product and
then deconstruct it into its parts.
Cheers
prev parent reply other threads:[~2022-10-20 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 6:36 [bug#58463] [PATCH] * doc: guix-cookbook: Add a "Guix API usage examples" Fulbert
2022-10-12 6:39 ` Fulbert
2022-10-18 12:09 ` Liliana Marie Prikler
2022-10-19 8:27 ` Fulbert
2022-10-19 10:12 ` zimoun
2022-11-30 16:54 ` Ludovic Courtès
2022-10-19 10:15 ` zimoun
2022-10-20 6:30 ` Liliana Marie Prikler [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88c58e9fe09076e2ea7e29d1424c8f6e47c7d9a8.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=58463@debbugs.gnu.org \
--cc=fulbert@bluewin.ch \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).