From: Giovanni Biscuolo <g@xelera.eu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Ryan Prior <rprior@protonmail.com>,
55013@debbugs.gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: bug#55013: Guix-emacs doesn't work
Date: Thu, 23 Mar 2023 18:06:58 +0100 [thread overview]
Message-ID: <874jqbxuq5.fsf@xelera.eu> (raw)
In-Reply-To: <878rfnig46.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2727 bytes --]
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Giovanni,
>
> thank you for testing.
>
> Can you please confirm that this is reproducible even in “guix shell
> -C”?
It's reproducible but with a minor difference: I also get a buffer named
*Guix Internal REPL* (see below)
I'm not able to start a graphical emacs container, I get only a text
interface (but I guess it's the same for the scope of this bug report):
--8<---------------cut here---------------start------------->8---
guix shell --preserve='^DISPLAY$' --preserve="^TERM" --preserve='^XAUTHORITY$' -C emacs-no-x-toolkit emacs-guix -- emacs -q
--8<---------------cut here---------------end--------------->8---
in *Messages* I get:
--8<---------------cut here---------------start------------->8---
Starting Guix REPL ... [5 times]
guix-geiser-eval: Error in evaluating guile expression: ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Unbound variable: %max-returned-list-size
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(emacs-guix) [1]>
--8<---------------cut here---------------end--------------->8---
but this time I get 2 REPL: one named "*Guix REPL*" with this prompt:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,m (emacs-guix)
While executing meta-command:
no code for module (guix ui)
scheme@(guile-user)>
--8<---------------cut here---------------end--------------->8---
and a second one named "*Guix Internal REPL*" (missing in my previous
tests) with this prompt:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,m (emacs-guix)
scheme@(emacs-guix)>
--8<---------------cut here---------------end--------------->8---
I missed to report that I also see a third *Geiser Messages* (also
present in my previous tests) buffer with this content:
--8<---------------cut here---------------start------------->8---
INFO: <3>: processed
INFO: REQUEST: <4>: (begin ((@ (system repl debug) terminal-width) 999) (quote ok))
INFO: RETORT: ((error (key . retort-syntax)) (output . "$8 = ok
scheme@(guile-user)> ") (debug))
INFO: <4>: processed
INFO: REQUEST: <5>: ,use (geiser emacs)
'done
INFO: RETORT: ((error (key . retort-syntax)) (output . "$9 = done
scheme@(guile-user)> ") (debug))
INFO: <5>: processed
INFO: REQUEST: <6>: ,geiser-eval (geiser evaluation) ge:set-warnings ((quote medium)) ()
INFO: RETORT: ((result "#<unspecified>") (output . ""))
INFO: <6>: processed
--8<---------------cut here---------------end--------------->8---
Thanks! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-03-23 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 23:46 bug#55013: Guix-emacs doesn't work Ryan Prior via Bug reports for GNU Guix
2022-04-21 9:50 ` Giovanni Biscuolo
2022-04-21 14:17 ` Giovanni Biscuolo
2022-04-22 5:27 ` Jan Nieuwenhuizen
2022-04-27 9:13 ` Giovanni Biscuolo
2022-04-27 9:16 ` Giovanni Biscuolo
2023-03-20 19:09 ` Ricardo Wurmus
2023-03-22 6:51 ` Giovanni Biscuolo
2023-03-23 13:32 ` Giovanni Biscuolo
2023-03-23 14:10 ` Giovanni Biscuolo
2023-03-23 14:11 ` Giovanni Biscuolo
2023-03-23 16:31 ` Ricardo Wurmus
2023-03-23 17:06 ` Giovanni Biscuolo [this message]
2023-03-25 21:00 ` Ryan Prior via Bug reports for GNU Guix
2023-03-25 22:46 ` Ricardo Wurmus
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=874jqbxuq5.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=55013@debbugs.gnu.org \
--cc=janneke@gnu.org \
--cc=rekado@elephly.net \
--cc=rprior@protonmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).