unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: exploring the code
Date: Tue, 19 Jul 2016 00:27:34 +0200	[thread overview]
Message-ID: <CAJ98PDwPp_A86B4rKC9f9Up0HJtxGsVFQeu+o1zsesvUH3bVSQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

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

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

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'd like Geiser to work on all the symbols, though.

[-- Attachment #2: Type: text/html, Size: 1224 bytes --]

             reply	other threads:[~2016-07-18 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 22:27 Catonano [this message]
2016-07-19 12:31 ` exploring the code 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

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=CAJ98PDwPp_A86B4rKC9f9Up0HJtxGsVFQeu+o1zsesvUH3bVSQ@mail.gmail.com \
    --to=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).