From: Munyoki Kilyungi <bonfacemunyoki@gmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guile-user@gnu.org
Subject: Re: Geiser+Guile For Remote Connections: "geiser-repl--wait-for-prompt: No prompt found!"
Date: Tue, 05 Jul 2022 10:55:49 +0300 [thread overview]
Message-ID: <86mtdot2m2.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <H34-2gYDF8Cf2Yt3nrSqlro3juqrAXENvnZaY1j5jcuHAviNzZNZw1AegP6TM3DP-6jX7m_562329tX9jId77yxhFFUIoc3gO9HthMavZ6U=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Luis Felipe <luis.felipe.la@protonmail.com>
anaandika:
> Hello Munyoki Kilyungi,
Hi Luis Felipe!
>> Any
>> one know how to fix the "No prompt found!" Or
>> better yet, how would you specify, with Geiser,
>> what Guile version to use on a per-project basis?
>
> I filed a bug report about that to Guix a couple of years ago, and it seems the problem comes from the "~/.guile" file. Removing it, for example, fixed the problem for me (See https://issues.guix.gnu.org/35727).
Thanks for this. Removing "~/.guile" fixes things
for me too, albeit it being a bit of an
inconvenience. This still is unresolved to date
unfortunately. FWIW, I don't think it's a Guix
problem, but a Guile issue.
--
(Life is like a pencil that will surely run out,
but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
(hkp://keys.gnupg.net))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
prev parent reply other threads:[~2022-07-05 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 23:34 Geiser+Guile For Remote Connections: "geiser-repl--wait-for-prompt: No prompt found!" Munyoki Kilyungi
2022-07-04 23:51 ` Luis Felipe
2022-07-05 7:55 ` Munyoki Kilyungi [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=86mtdot2m2.fsf@bonfacemunyoki.com \
--to=bonfacemunyoki@gmail.com \
--cc=guile-user@gnu.org \
--cc=luis.felipe.la@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.
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).