unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: exploring the code
Date: Tue, 19 Jul 2016 16:55:18 +0200	[thread overview]
Message-ID: <87h9bl65k9.fsf@gnu.org> (raw)
In-Reply-To: <877fchn70q.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 19 Jul 2016 14:31:49 +0200")

Hi,

ludo@gnu.org (Ludovic Courtès) writes:

> 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.

'C-c C-k' (geiser-compile-current-buffer) works most of the time,
however this is not a silver bullet.  For example:

--8<---------------cut here---------------start------------->8---
;;; foo.scm
(define (where-is-foo)
  (display "foo!\n"))

(where-is-foo)
--8<---------------cut here---------------end--------------->8---

'M-.' when the point is on 'where-is-foo' procedure call won't find the
procedure definition even after 'C-c C-k'.  It only works in the context
of a module.

My point is that Geiser should not be expected to be 100% reliable.
'M-x rgrep' is sometimes a helpful complement.  ;)

Thanks,

-- 
Mathieu Lirzin

  reply	other threads:[~2016-07-19 14:55 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 [this message]
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=87h9bl65k9.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=ludo@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).