all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: inside the Guile REPL
Date: Tue, 16 Jun 2015 13:38:18 +0200	[thread overview]
Message-ID: <877fr3x4r9.fsf@gnu.org> (raw)
In-Reply-To: <20150616070443.GA23824@thebird.nl> (Pjotr Prins's message of "Tue, 16 Jun 2015 09:04:43 +0200")

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> I have started to document how to use Guix from the Guile REPL.
> Tips/hints wanted from experienced hackers! This is not only to keep
> my memory fresh, it may be useful for others.
>
>   https://github.com/pjotrp/guix-notes/blob/master/HACKING.org#debugging-the-package

Nice work!

I think it would be nice to see what could be folded into the manual.

The “Defining Packages” section attempts to get the reader started with
writing package definitions, also giving references to the various tools
(‘guix import’, ‘guix hash’, etc.)  Do you think there are things that
could be presented differently or added to that section?

The API, things like bags, and using the REPL are largely undocumented
in the manual.  Regarding the REPL, we probably don’t want to duplicate
what’s already in the Guile manual.

However, I agree that giving an example of how to use the REPL
specifically with Guix would be welcome.  Would you like to propose a
patch?  This could be a section below “Defining Packages” with the
transcript of a simple REPL session and cross-references to the relevant
parts of the Guile manual.

The part about patches should be mostly covered by the new “Submitting
Patches” section of the manual, but again, improvements are always
welcome!

Thanks,
Ludo’.

  reply	other threads:[~2015-06-16 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16  7:04 inside the Guile REPL Pjotr Prins
2015-06-16 11:38 ` Ludovic Courtès [this message]
2015-06-16 14:44   ` Pjotr Prins
2015-06-16 12:26 ` Amirouche Boubekki
2015-06-16 17:25 ` Mark H Weaver

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877fr3x4r9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.