From: Jake Shilling <shilling.jake@gmail.com>
To: jgart <jgart@dismail.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Fri, 11 Nov 2022 17:06:07 -0500 [thread overview]
Message-ID: <87fsepqh80.fsf@gmail.com> (raw)
In-Reply-To: <20221111154213.GB25240@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
>
> Maybe it only works out of the box as described in the manual if you
> happen to be on Guix System but not on Void Linux?
I haven't spent a lot of time with Guix on a foreign distro, but whenver
I have tried it there's been lots of weird problems that I didn't
understand.
>
> What can I do to debug what the issue is on my system (void linux)
> with geiser?
I'm sure someone who actually knows what they're doing could help more
than me, but my thought would be to start by debugging guile outside of
Geiser. I would try to spin up a repl and see if I could import one of
the modules from ~/guix and check out what the %load-path ends up being.
--
Best regards,
Jake Shilling
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-11-11 22:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 1:35 geiser-edit-symbol-at-point jgart
2022-11-11 1:39 ` geiser-edit-symbol-at-point jgart
2022-11-11 1:44 ` geiser-edit-symbol-at-point jgart
2022-11-11 14:31 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 16:17 ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 16:47 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 17:10 ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 18:40 ` geiser-edit-symbol-at-point jgart
2022-11-11 20:43 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 21:42 ` geiser-edit-symbol-at-point jgart
2022-11-11 21:45 ` geiser-edit-symbol-at-point jgart
2022-11-11 22:06 ` Jake Shilling [this message]
2022-11-11 22:15 ` geiser-edit-symbol-at-point jgart
2022-11-12 0:07 ` geiser-edit-symbol-at-point jgart
2022-11-12 0:12 ` geiser-edit-symbol-at-point jgart
2022-11-12 15:48 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 15:01 ` geiser-edit-symbol-at-point jgart
2022-11-14 15:16 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 22:38 ` geiser-edit-symbol-at-point jgart
2022-11-15 1:31 ` geiser-edit-symbol-at-point Jake Shilling
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=87fsepqh80.fsf@gmail.com \
--to=shilling.jake@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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).