From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Geiser manual lookups broken with Guile
Date: Thu, 17 Jan 2019 20:23:44 +0100 [thread overview]
Message-ID: <87munzf5q7.fsf@elephly.net> (raw)
In-Reply-To: <87sgxrqhfi.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> I've been annoyed by this issue ever since I started using Guile and
> today I finally found time to get to the root of it:
>
> https://gitlab.com/jaor/geiser/issues/252
>
> Since there are a lot of Guile+Geiser users in this community, I'm
> wondering if you people experience the same issue.
If no documentation is shown at all and a Guile REPL is connected to
your Emacs buffer, then you need to load some modules in the REPL
session first.
--
Ricardo
next prev parent reply other threads:[~2019-01-17 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 18:15 Geiser manual lookups broken with Guile Pierre Neidhardt
2019-01-17 19:23 ` Ricardo Wurmus [this message]
2019-01-17 20:15 ` Pierre Neidhardt
2019-01-18 10:14 ` swedebugia
2019-01-19 3:37 ` Maxim Cournoyer
2019-01-19 16:43 ` Maxim Cournoyer
2019-01-19 22:09 ` Ludovic Courtès
2019-01-20 20:17 ` Pierre Neidhardt
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=87munzf5q7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
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).