Is this the way geiser works for others?

Is this the way geiser works for others?

[myglc2]

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

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?

TIA - George

I'm running GuixSD and emacs-guix built from recent git pulls.

GNU Guix 0.12.0
Emacs-Guix 0.3

emacs config:


[-- Attachment #2: guix.el --]
[-- Type: application/emacs-lisp, Size: 698 bytes --]

Re: Is this the way geiser works for others?

[Alex Kost]

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

-- 
Alex

Re: Is this the way geiser works for others?

[myglc2]

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?

Thank you for helping me to get "C-c . u", "M-." working.  For others
that may care, here are fixes I needed:


Problem:

emacs-guix development mode (C-c . _) functions don't work:

Fix: add in emacs `init ...

(add-hook 'scheme-mode-hook 'guixlevell-mode)


Problem:

'C-c . u' is horribly slow and 'M-.' produces  ...

geiser-ediot-symbol-at-point: Couldn’t find edit location for ’define-module’

As you explained off-list ...

> guix is still compiled with Guile 2.0! (Ludovic plans to switch Guix
> to Guile 2.2 really soon).  And these two Guile versions are
> incompatible!  So whenever you start guile (no matter in a shell or
> with "M-x run-guile" or via Guix REPL), guile 2.2 doesn't find
> compatible .go files (that's where errors come from) and it compiles
> .scm again for 2.2 version.

Fix: remove guile from user and/or system profiles!


Problem:

'C-c . u' is not so horribly slow and 'M-.' produces ....

geiser-ediot-symbol-at-point: Couldn’t find edit location for ’define-module’

Fix: remove ...

(with-eval-after-load 'geiser-guile
   (add-to-list 'geiser-guile-load-path "~/src/guix"))

...  from emacs init. Add this to .bash_profile ...

export GUILE_LOAD_PATH="$HOME/src/guix${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH"
export GUILE_LOAD_COMPILED_PATH="$HOME/src/guix${GUILE_LOAD_COMPILED_PATH:+:}$GUILE_LOAD_COMPILED_PATH"

Re: Is this the way geiser works for others?

[Alex Kost]

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

Re: Is this the way geiser works for others?

[myglc2]

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