From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: exploring the code
Date: Tue, 19 Jul 2016 22:15:35 +0200 [thread overview]
Message-ID: <878twxfkpk.fsf@gnu.org> (raw)
In-Reply-To: <87inw1d1pj.fsf@gmail.com> (Alex Kost's message of "Tue, 19 Jul 2016 19:36:40 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2016-07-19 15:31 +0300) wrote:
>
>> Catonano <catonano@gmail.com> skribis:
>>
>>> I opened the file guix/scripts/build.scm in Emacs
>>>
>>> For Geiser to be able to jump to the definition of a symbol at point
>>> or to open a documentation buffer, I need the Guile REPL to "load" the
>>> file
>>>
>>> C-x C-b does the trick, but I see this error in the REPL, then
>>>
>>> http://paste.lisp.org/display/320775
>>
>> I use C-c C-k (geiser-compile-current-buffer), which works well for me.
>
> I never liked this command. I found it too slow, and I didn't
> understand why it does so much, I always prefered
> ",use(<current-module>)". That's why I added "C-c . u" key to
> guix-devel-mode. It does exactly that: uses the current module.
Good point, I should train my muscle memory to use this one.
Maybe Geiser should provide it in the first place? (Basically a variant
of C-c C-a that doesn’t jump to the REPL.)
Ludo’.
prev parent reply other threads:[~2016-07-19 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 22:27 exploring the code Catonano
2016-07-19 12:31 ` Ludovic Courtès
2016-07-19 14:55 ` Mathieu Lirzin
2016-07-19 19:27 ` Amirouche Boubekki
2016-07-21 3:34 ` Catonano
2016-07-19 16:36 ` Alex Kost
2016-07-19 20:15 ` Ludovic Courtès [this message]
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=878twxfkpk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=help-guix@gnu.org \
/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).