From: Alex Kost <alezost@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Is this the way geiser works for others?
Date: Fri, 14 Apr 2017 20:28:10 +0300 [thread overview]
Message-ID: <87r30uzyol.fsf@gmail.com> (raw)
In-Reply-To: <8660i7j663.fsf@gmail.com> (myglc2@gmail.com's message of "Fri, 14 Apr 2017 12:38:28 -0400")
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’
>>>
>>> If I select 'emacs-build-system' and press M-. I see ...
>>>
>>> geiser-edit-symbol-at-point: Couldn’t find edit location for
>>> ’emacs-build-system’
>>>
>>> Is this how geiser works for others?
>>
>> Yes, it is, that's why I added "C-c . u" to Emacs-Guix: before you can
>> jump to a definition, you need to use the current module, so after
>> pressing "C-c . u", "M-." on 'emacs-build-system' should work.
>>
>> 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.
> Thank you for helping me to get "C-c . u", "M-." working. For others
> that may care, here are fixes I needed:
No problem.
> Problem:
>
> emacs-guix development mode (C-c . _) functions don't work:
>
> Fix: add in emacs `init ...
>
> (add-hook 'scheme-mode-hook 'guixlevell-mode)
typo: 'guix-devel-mode
--
Alex
next prev parent reply other threads:[~2017-04-14 17:28 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 [this message]
2017-04-14 18:38 ` myglc2
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=87r30uzyol.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.com \
/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).