unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: extending the documentation of the Scheme API
Date: Sun, 29 Dec 2019 09:20:57 +0100	[thread overview]
Message-ID: <87v9pzv8ye.fsf@gnu.org> (raw)
In-Reply-To: <87sgleprp6.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 20 Dec 2019 23:17:41 +0100")

Ricardo Wurmus writes:

Hello Ricardo

> we have lots of nice macros and procedures in Guix that aren’t
> documented beyond their docstrings.
>
> Should we snarf the docstrings and add them to the manual?

If you are talking about guix records and (guix build utils); I think it
would be great if these were split off from Guix.  I guess that
documenting them right now, as a first step, would be nice in itself.

I am not sure where Guix records could go (Guile?); but many (guix build
utils) could move to Gash or a common library even.  WDYT?

Greetings,
jannneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  parent reply	other threads:[~2019-12-29  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 22:17 extending the documentation of the Scheme API Ricardo Wurmus
2019-12-21  1:45 ` John Soo
2019-12-21  4:04 ` Jesse Gibbons
2019-12-21 12:24   ` Pjotr Prins
2019-12-23 11:44 ` Bengt Richter
2019-12-29  8:20 ` Jan Nieuwenhuizen [this message]
2019-12-30 18:38   ` Ludovic Courtès

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=87v9pzv8ye.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).