all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: Geiser manual lookups broken with Guile
Date: Fri, 18 Jan 2019 22:37:54 -0500	[thread overview]
Message-ID: <87va2lnwq5.fsf@gmail.com> (raw)
In-Reply-To: <1e4f100a-f8b5-08ad-9ed5-b8f68456b787@riseup.net> (swedebugia's message of "Fri, 18 Jan 2019 11:14:49 +0100")

swedebugia <swedebugia@riseup.net> writes:

> On 2019-01-17 20:23, Ricardo Wurmus wrote:
>>
>> 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.
>
> A ha! Now it works better.
> I typed in this: 
> ",use(guix)"
> and now it shows me docstrings from guix. 😀
>
> Would it be possible to do this automatically?

I usually use C-c C-a, which is bound to
(geiser-mode-switch-to-repl-and-enter). It starts a Guile REPL if it wasn't
already, and enters the module corresponding to that of the buffer you
are visiting.

HTH!

Maxim

  reply	other threads:[~2019-01-19  3:38 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
2019-01-17 20:15   ` Pierre Neidhardt
2019-01-18 10:14   ` swedebugia
2019-01-19  3:37     ` Maxim Cournoyer [this message]
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

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

  git send-email \
    --in-reply-to=87va2lnwq5.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=swedebugia@riseup.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 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.