unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: jgart <jgart@dismail.de>
To: Jake Shilling <shilling.jake@gmail.com>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Fri, 11 Nov 2022 15:42:13 -0600	[thread overview]
Message-ID: <20221111154213.GB25240@dismail.de> (raw)
In-Reply-To: <877d01dxxt.fsf@gmail.com>

On Fri, 11 Nov 2022 15:43:26 -0500 Jake Shilling <shilling.jake@gmail.com> wrote:
> On 2022-11-11 12:40, jgart@dismail.de wrote:
> 
> > On Fri, 11 Nov 2022 09:31:40 -0500 Jake Shilling <shilling.jake@gmail.com> wrote:

> That is definitly enouhg to make sure ~/guix is processed by guile and
> then Gieser. 

Hi Jake, I'll get back to your points above but I wanted to clarify that
it is not enough to just set the src repo checkout for Guix on a foreign
distro. Atleast, not on void linux.

I'm not able to geiser-edit-symbol-at-point at all successfully after setting
the basics as described in the Guix manual and as I described prior.

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?

Does Geiser work fine after being configured as described in
the guix manual on Ubuntu or Debian?

What can I do to debug what the issue is on my system (void linux)
with geiser?

I should check to see if some guix specific environment variables are
missing or improperly set in my bashrc or bash_profile?

I'm using bash on void linux.

all best,

jgart



  reply	other threads:[~2022-11-11 21:43 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         ` jgart [this message]
2022-11-11 21:45           ` geiser-edit-symbol-at-point jgart
2022-11-11 22:06           ` geiser-edit-symbol-at-point Jake Shilling
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=20221111154213.GB25240@dismail.de \
    --to=jgart@dismail.de \
    --cc=help-guix@gnu.org \
    --cc=shilling.jake@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).