From: ludo@gnu.org (Ludovic Courtès)
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: exploring the code
Date: Tue, 19 Jul 2016 14:31:49 +0200 [thread overview]
Message-ID: <877fchn70q.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDwPp_A86B4rKC9f9Up0HJtxGsVFQeu+o1zsesvUH3bVSQ@mail.gmail.com> (catonano@gmail.com's message of "Tue, 19 Jul 2016 00:27:34 +0200")
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.
Not sure what the problem is here.
> After that, many symbols become available anyway: I can jump to their
> definition and I can have doc buffers popping up
>
> All but one: "options->derivations" on line 670
Works for me after C-c C-k. :-)
Could you try this and report back? It’s a good idea to pre-build Guix
before, using ‘make’, so that Geiser doesn’t end up recompiling
everything.
> I'm doing this because I'd like to redo in the REPL what the command
> "guix build blah" does. At least some parts of it
>
> In order to make it less abstract in my mind, to get aquainted with
> the build subsystem. I need to see some procedures called and
> returning something, I need to see macros expanded.
>
> I hope you understand
>
> If anyone can suggest a better way to get aquainted with the build
> subsystem I'm all ears.
I think you’re right, it’s a very good idea to explore Guix this way.
This is more or less the approach I took in
<https://audio-video.gnu.org/video/misc/2016-01__GNU_Guix__Your_Distro_is_a_Scheme_Library.webm>,
so you might find it useful (you might also have suggestions on how to
improve this talk, which would be more than welcome!).
HTH,
Ludo’.
next prev parent reply other threads:[~2016-07-19 12:31 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 [this message]
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
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=877fchn70q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=catonano@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).