From: Suhail Singh <suhailsingh247@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: Suhail Singh <suhailsingh247@gmail.com>, 74250@debbugs.gnu.org
Subject: bug#74250: emacs-guix: guix-pull invalid input error
Date: Wed, 20 Nov 2024 16:33:12 -0500 [thread overview]
Message-ID: <87wmgxa8vb.fsf@gmail.com> (raw)
In-Reply-To: <87zflt63qr.fsf@librehacker.com> (Christopher Howard's message of "Wed, 20 Nov 2024 11:37:32 -0900")
Christopher Howard <christopher@librehacker.com> writes:
> So, my experiment was to see if I could run the scheme command «(guix-command
> "pull")» from the console instead, just using guix repl. However, since guix
> repl will not load any emacs-guix scheme code, I had to add
> "/home/christopher/Repos/emacs-guix/scheme" to the GUILE_LOAD_PATH in order to
> be able to load (emacs-guix) module.
>
> Hopefully that clarifies what I am seeing.
I see. Thank you for clarifying.
> Looking at this now, I see that there are significant differences between the
> paths for paths in %load-path vs paths in GUILE_LOAD_PATH.
Yes.
The "guix-module-union" entry I alluded to was one of the differences I
had observed between %load-path values between "guile" and "guix repl"
when both were invoked from the commandline (outside of Emacs). It may
help for a future version of emacs-guix to take some steps to resolve
said differences, if you find them to be material / problematic.
--
Suhail
next prev parent reply other threads:[~2024-11-20 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:53 bug#74250: emacs-guix: guix-pull invalid input error Christopher Howard
2024-11-19 20:55 ` Christopher Howard
2024-11-20 18:30 ` Christopher Howard
2024-11-20 19:06 ` Suhail Singh
2024-11-20 19:23 ` Christopher Howard
2024-11-20 19:50 ` Suhail Singh
2024-11-20 20:37 ` Christopher Howard
2024-11-20 21:33 ` Suhail Singh [this message]
2024-11-21 20:27 ` Christopher Howard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmgxa8vb.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=74250@debbugs.gnu.org \
--cc=christopher@librehacker.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.