From: zimoun <zimon.toutoune@gmail.com>
To: mirai@makinata.eu, 59712@debbugs.gnu.org
Cc: Bruno Victal <mirai@makinata.eu>
Subject: [bug#59712] [PATCH] doc: Suggest guile-readline and guile-colorized.
Date: Wed, 30 Nov 2022 09:37:36 +0100 [thread overview]
Message-ID: <86lens6dnz.fsf@gmail.com> (raw)
In-Reply-To: <0c0dad2622d0377c4022cd7e8663cf0bad0c8be1.1669774979.git.mirai@makinata.eu>
Hi,
On Wed, 30 Nov 2022 at 02:23, mirai@makinata.eu wrote:
> +guix shell -D guix help2man git strace guile-readline guile-colorized --pure
The package guile-readline requires to be activated, no?
For guile-colorized, never used. :-)
On one hand, I agree that smoothing the experience with “guix repl” is
worth. On the other hand, I think it better to reduce the barrier by
suggesting out-of-the-box packages in the Contributing section.
Well, instead, I am proposing to put this recommendation in this other
section (guix) The Perfect Setup. For example, better worded :-)
--8<---------------cut here---------------start------------->8---
The Perfect Setup to hack on Guix is basically the perfect setup used
for Guile hacking (*note (guile)Using Guile in Emacs::). First, the
experience is smooth when the packages guile-readline and
guile-colorized are installed and configured. We recommend this
~/.guile,
(use-modules
(ice-9 readline)
(ice-9 format)
(ice-9 pretty-print))
(activate-readline)
Then, you need more than an editor, you need Emacs
(https://www.gnu.org/software/emacs), empowered by the wonderful Geiser
(https://nongnu.org/geiser/). To set that up, run:
--8<---------------cut here---------------end--------------->8---
WDYT?
Cheers,
simon
next prev parent reply other threads:[~2022-11-30 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 2:23 [bug#59712] [PATCH] doc: Suggest guile-readline and guile-colorized mirai
2022-11-30 8:37 ` zimoun [this message]
2022-11-30 12:11 ` mirai
2022-12-02 18:59 ` mirai
2022-12-14 13:33 ` zimoun
2022-12-14 11:39 ` [bug#59712] [DOCUMENTATION] " Ludovic Courtès
2022-12-28 17:28 ` mirai
2022-12-30 14:37 ` zimoun
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=86lens6dnz.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=59712@debbugs.gnu.org \
--cc=mirai@makinata.eu \
/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).