From: Marius Bakke <marius@gnu.org>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>,
guix-devel <guix-devel@gnu.org>
Subject: Re: guile-readline bug -- readline module not available
Date: Sat, 25 Jul 2020 16:55:59 +0200 [thread overview]
Message-ID: <87v9ibve2o.fsf@gnu.org> (raw)
In-Reply-To: <CAFkJGRcTdWAKq8F3eSyDS1RedXoLEsvX=gafuBoaFYrFEsknmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Josh Marshall <joshua.r.marshall.1991@gmail.com> writes:
> Hello all,
>
> I ran into an issue where the readline module isn't available for the
> guile repl after installing `guile-readline`. It can be replicated
> via:
>
> `echo "(use-modules (ice-9 readline))" | guix environment --pure guile
> guile-readline -- guile`
>
> So with that, I'm pretty sure it isn't just me.
This is on a foreign distribution, right?
The '.guile' on Guix System has a trick that automatically loads
readline when available:
--8<---------------cut here---------------start------------->8---
$ cat ~/.guile
(cond ((false-if-exception (resolve-interface '(ice-9 readline)))
=>
(lambda (module)
;; Enable completion and input history at the REPL.
((module-ref module 'activate-readline))))
(else
(display "Consider installing the 'guile-readline' package for
convenient interactive line editing and input history.\n\n")))
--8<---------------cut here---------------end--------------->8---
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-25 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 22:32 guile-readline bug -- readline module not available Josh Marshall
2020-06-13 4:11 ` Jack Hill
2020-06-13 15:31 ` Josh Marshall
2020-06-13 19:09 ` Jack Hill
2020-07-25 14:55 ` Marius Bakke [this message]
2020-07-25 16:18 ` Josh Marshall
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=87v9ibve2o.fsf@gnu.org \
--to=marius@gnu.org \
--cc=guix-devel@gnu.org \
--cc=joshua.r.marshall.1991@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 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.