unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Fulbert <fulbert@bluewin.ch>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 58463@debbugs.gnu.org
Subject: [bug#58463] [PATCH] * doc: guix-cookbook: Add a "Guix API usage examples"
Date: Wed, 19 Oct 2022 10:27:21 +0200	[thread overview]
Message-ID: <Y0+06VhZPI2y1fp8@bluewin.ch> (raw)
In-Reply-To: <b8c5100dba3bfca99dda3b4ffebe570800d17cec.camel@ist.tugraz.at>

Le Tue, Oct 18, 2022 at 02:09:57PM +0200, Liliana Marie Prikler a écrit :
> Hi Fulbert,


Hello Liliana and thank you for your remarks.

As it stands, it's only a proposal and I don't want to spend more
time on it unless I am sure Guix [doc] maintainers think it would
make a relevant addition to the Docbook.

Your remarks make sense to me, and I'd gladly improve it as
suggested, except for this : If by “structure” you mean Simon
Tournier presentation flow from REPL to script and finaly
extensions, then I will not be the right person to adapt it for the
Docbook, as I found the video *volumen* to follow a clean, logical
and clear path and to which the light addition of this
*codex+hypertext* transcript adds quick/random access and
searcheability. At present state (including the improvement you
suggested), it would be a good balance *for my taste* : easy access
with minimal discourse for maximal practical information.

Best regards.




  reply	other threads:[~2022-10-19  8:28 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 [this message]
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

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=Y0+06VhZPI2y1fp8@bluewin.ch \
    --to=fulbert@bluewin.ch \
    --cc=58463@debbugs.gnu.org \
    --cc=liliana.prikler@ist.tugraz.at \
    /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).