GNU bug report logs - #73462
emacs-guix: shell commands broken

Previous Next

Package: guix;

Reported by: Christopher Howard <christopher <at> librehacker.com>

Date: Tue, 24 Sep 2024 21:59:02 UTC

Severity: normal

Full log


View this message in rfc822 format

From: Christopher Howard <christopher <at> librehacker.com>
To: "Suhail Singh" <suhailsingh247 <at> gmail.com>
Cc: Katherine Cox-Buday <cox.katherine.e+guix <at> gmail.com>, Liliana Marie Prikler <liliana.prikler <at> gmail.com>, Andrew Tropin <andrew <at> trop.in>, 73462 <at> debbugs.gnu.org, Guix Devel <guix-devel <at> gnu.org>, guix-patches <at> gnu.org
Subject: bug#73462: [PATCH] emacs-guix: shell commands broken
Date: Wed, 06 Nov 2024 06:50:00 -0900
[0001-Provides-work-around-for-https-issues.guix.gnu.org-i.patch (text/x-patch, attachment)]
[Message part 2 (text/plain, inline)]
I've attached a patch for the emacs-guix source which works around this issue. It modifies the REPL starting process for the Internal REPL, so that the (guix gexp) module is explicitly (re)loaded, which allows to reader syntax to work when the other modules load. I do not know why this should be necessary.

I wondered if there is some subtle difference here when dealing with a REPL that is accessed over a socket, as is the case with the Internal REPL. But I can't reproduce the problem on the command-line, outside of emacs-guix, using sockets.

With this patch, the "guix shell command" popup opens, though I see there is something wrong with the popup itself. It does not ask for a command to run, and the popup options only attempt to run an empty command. But I could investigate that in a separate bug.

Troubleshooting/testing was done with GNU Emacs 30.0.92 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.41, cairo version 1.18.0) of 2024-10-29.

-- 
Christopher Howard

This bug report was last modified 281 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.