From: Antonio Carlos Padoan Junior via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Mekeor Melire <mekeor@posteo.de>
Cc: 35727@debbugs.gnu.org, luis.felipe.la@protonmail.com, sirgazil@zoho.com
Subject: bug#35727: Connecting Geiser to Guile listening to a socket: No prompt found! (.guile to blame)
Date: Mon, 12 Dec 2022 16:44:15 +0100 [thread overview]
Message-ID: <87r0x4eieo.fsf@yahoo.com.br> (raw)
In-Reply-To: <87mt7s7nfm.fsf@posteo.de> (Mekeor Melire's message of "Mon, 12 Dec 2022 13:32:39 +0000")
Mekeor Melire <mekeor@posteo.de> writes:
>
> Does it work when you start the Guile REPL with an
> environment-variable called INSIDE_EMACS? That way, it worked fine
> for me:
>
> #+begin_src sh
> INSIDE_EMACS=true guix repl --listen=tcp:37146
> #+end_src
>
> If this works, then I'd suggest that this is not a bug but rather
> you got to know that you need to deliver that environment variable
> to guix/guile. We could then close this ticket.
>
> Personally, I think this is only a bug in Geiser which should be
> able to parse colored prompts.
>
My feedback:
using INSIDE_EMACS=true works as well as starting guix repl from eshell.
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-17 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 11:17 bug#35727: Connecting Geiser to Guile listening to a socket: No prompt found! (.guile to blame) sirgazil
2020-12-08 16:45 ` Luis Felipe via Bug reports for GNU Guix
2022-12-12 13:32 ` Mekeor Melire
2022-12-12 15:44 ` Antonio Carlos Padoan Junior via Bug reports for GNU Guix [this message]
2023-01-12 17:32 ` Luis Felipe via Bug reports for GNU Guix
2023-01-12 19:20 ` Luis Felipe via Bug reports for GNU Guix
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=87r0x4eieo.fsf@yahoo.com.br \
--to=bug-guix@gnu.org \
--cc=35727@debbugs.gnu.org \
--cc=acpadoanjr@yahoo.com.br \
--cc=luis.felipe.la@protonmail.com \
--cc=mekeor@posteo.de \
--cc=sirgazil@zoho.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).