From: myglc2 <myglc2@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Is this the way geiser works for others?
Date: Fri, 14 Apr 2017 14:38:49 -0400 [thread overview]
Message-ID: <86y3v2j0li.fsf@gmail.com> (raw)
In-Reply-To: <87r30uzyol.fsf@gmail.com> (Alex Kost's message of "Fri, 14 Apr 2017 20:28:10 +0300")
On 04/14/2017 at 20:28 Alex Kost writes:
> myglc2 (2017-04-14 12:38 -0400) wrote:
>
>> On 04/12/2017 at 12:11 Alex Kost writes:
>>
>>> myglc2 (2017-04-12 00:21 -0400) wrote:
>>>
>>>> I am starting to wonder if something is horribly wrong. Why? Well, if I
>>>> do 'M-x guix-edit emacs.scm', do 'M-x run-geiser', select
>>>> 'define-module', and press M-. I see ...
>>>>
>>>> geiser-edit-symbol-at-point: Couldn’t find edit location for
>>>> ’define-module’
[...]
>>> As for 'define-module', you'll never be able to "edit" it with "M-.",
>>> because it is internal. See <https://github.com/jaor/geiser/issues/160>.
>>
>> This puzzles me. If I use etags I can get *xref* to show ...
>>
>> /home/g1/src/guix/test-tmp/store/ywpd8i2s87fzmzfpl2h96m949p7rwmcd-guile-bootstrap-2.0/share/guile/2.0/ice-9/curried-definitions.scm
>> 44: (define-syntax define-public
>> /home/g1/src/guix/test-tmp/store/ywpd8i2s87fzmzfpl2h96m949p7rwmcd-guile-bootstrap-2.0/share/guile/2.0/ice-9/boot-9.scm
>> 3576: (define-syntax define-public
>> /home/g1/src/guix/test-tmp/store/v229gc83qn1j7c7l6r65bfw2b8j7rx2w-boot-9.scm
>> 3685: (define-syntax define-public
>>
>> Isn't one of these what I want to look at?
>
> I don't really know how Geiser finds the definitions for jumping, but
> there are some "internal" things that Geiser can't find (for example,
> "cons", "append", "with-output-to-file", etc.). I just don't know
> what is the definition of the term "internal" in this context,
> i.e. what can be found and what cannot.
OK, I believe you. But here is what would happen in my dream world:
Because I don't understand the guix-verse I decide to look at ... guix
source. I use emacs-guix because I am sure it will help me do that ;-)
When I see something interesting I push some button and WOW, emacs-guix
shows me the relevant source ;-) I don't need to know whether the source
came from geiser, tags, brute force search of my whole hard drive, or
Jupiter ;-)
BTW, I had to turn geiser mode off to get the *xref* above, and
Correction: *xref* for 'define-module' is actually
*xref*
/home/g1/src/guix/test-tmp/store/ywpd8i2s87fzmzfpl2h96m949p7rwmcd-guile-bootstrap-2.0/share/guile/2.0/ice-9/boot-9.scm
3402: (define-syntax define-module
/home/g1/src/guix/test-tmp/store/v229gc83qn1j7c7l6r65bfw2b8j7rx2w-boot-9.scm
3511: (define-syntax define-module
prev parent reply other threads:[~2017-04-14 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 4:21 Is this the way geiser works for others? myglc2
2017-04-12 9:11 ` Alex Kost
2017-04-14 16:38 ` myglc2
2017-04-14 17:28 ` Alex Kost
2017-04-14 18:38 ` myglc2 [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=86y3v2j0li.fsf@gmail.com \
--to=myglc2@gmail.com \
--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).