From: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>
To: Mekeor Melire <mekeor@posteo.de>
Cc: guix-devel@gnu.org
Subject: Re: geiser and guix repl
Date: Mon, 12 Dec 2022 11:28:11 +0100 [thread overview]
Message-ID: <87v8mgex1g.fsf@yahoo.com.br> (raw)
In-Reply-To: <87fsdlwg8l.fsf@posteo.de> (Mekeor Melire's message of "Mon, 12 Dec 2022 01:38:24 +0000")
Mekeor Melire <mekeor@posteo.de> writes:
>
> By the way, personally, starting "guix repl --listen=tcp:37146"
> from terminal and then running M-x geiser-connect makes Emacs
> freeze for me. Do you experience the same?
>
Yes, that was exactly my issue.
The .guile file that you mentioned, the one provided automatically by
Guix system (I was not aware of it), was responsible for the problem at
the end. This script provide colors and other utilities when using guile
from a terminal. If you connect to the guile session using geiser, you
have a session in emacs with a colored prompt as well (it is necessary
to use C-g to escape the hang). The colors in prompt are not properly parsed
by geiser, I think so.
I deleted my .guix file and tried again. Everything was fine.
Now that I learned that .guix file was automatically created (and it was not
something I eventually created myself), I think this issue is something
that should be documented/clarified somewhere or improved.
I will try to launch guix repl from a eshell and check if the .guile
script recognizes that the color should be disabled.
Best regards,
--
Antonio Carlos PADOAN JUNIOR
GPG fingerprint:
243F 237F 2DD3 4DCA 4EA3 1341 2481 90F9 B421 A6C9
next prev parent reply other threads:[~2022-12-12 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sfhmnu8k.fsf.ref@yahoo.com.br>
2022-12-11 9:51 ` geiser and guix repl Antonio Carlos Padoan Junior
2022-12-11 11:39 ` Antonio Carlos Padoan Junior
2022-12-12 1:38 ` Mekeor Melire
2022-12-12 10:28 ` Antonio Carlos Padoan Junior [this message]
2022-12-12 13:17 ` Luis Felipe
2022-12-12 13:28 ` Mekeor Melire
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=87v8mgex1g.fsf@yahoo.com.br \
--to=acpadoanjr@yahoo.com.br \
--cc=guix-devel@gnu.org \
--cc=mekeor@posteo.de \
/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.