From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: 74484@debbugs.gnu.org
Subject: bug#74484: reader syntax trouble across socket
Date: Mon, 09 Dec 2024 18:08:18 +0100 [thread overview]
Message-ID: <8734iwn5rx.fsf@gnu.org> (raw)
In-Reply-To: <87a5druh4i.fsf@librehacker.com> (Christopher Howard's message of "Fri, 22 Nov 2024 11:51:25 -0900")
Hi Christopher,
Christopher Howard <christopher@librehacker.com> scribans:
> scheme@(guile-user)> ,m (emacs-guix)
> scheme@(emacs-guix)> (guix-command "pull")
> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
> Building from this channel:
> guix https://git.savannah.gnu.org/git/guix.git 8a7bd21
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> /gnu/store/hhnw8gr26smc267yy2hzk57p4b0g6iyb-guix-8a7bd21/build-aux/build-self.scm:84:18: Unknown # object: "#~"
The read syntax for #~ (gexp) is installed by loading the (guix gexp)
module or simply the (guix) module, which loads (guix gexp).
It seems that somehow Emacs-Guix does not load (guix gexp) upfront.
It’s fishy though because (guix scripts pull) definitely loads (guix
gexp), directly and indirectly.
Ludo’.
prev parent reply other threads:[~2024-12-09 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 20:51 bug#74484: reader syntax trouble across socket Christopher Howard
2024-12-09 17:08 ` Ludovic Courtès [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734iwn5rx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74484@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.
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).