GNU bug report logs - #35727
Connecting Geiser to Guile listening to a socket: No prompt found! (.guile to blame)

Previous Next

To reply to this bug, email your comments to 35727 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: sirgazil <sirgazil <at> zoho.com>
To: "bug-guix" <bug-guix <at> gnu.org>
Subject: Connecting Geiser to Guile listening to a socket: No prompt found!
 (.guile to blame)
Date: Tue, 14 May 2019 06:17:19 -0500

Hi,

I'm getting a "No prompt found!" error when I try to connect Geiser to a Guile REPL like this:

1. In a terminal, run "$ guile --listen=/tmp/guile-socket"
2. In Emacs, "M-x geiser-connect-local", then "guile", and finally "/tmp/guile-socket"

When the Guile REPL start in Emacs, I get a "No prompt found!" in the echo area, and the prompt in the REPL looks like this:

https://multimedialib.files.wordpress.com/2019/05/emacs-geiser-guile-repl-no-prompt-found-2019-05-13.png

After trying some things out with help from str1ngs on #guix, we found out that the problem is related to the ".guile" file that seems to be generated by the system by default. In my case, ".guile" looks like this:

##########
(cond ((false-if-exception (resolve-interface '(ice-9 readline)))
       =>
       (lambda (module)
         ;; Enable completion and input history at the REPL.
         ((module-ref module 'activate-readline))))
      (else
       (display "Consider installing the 'guile-readline' package for
convenient interactive line editing and input history.\n\n")))

      (unless (getenv "INSIDE_EMACS")
        (cond ((false-if-exception (resolve-interface '(ice-9 colorized)))
               =>
               (lambda (module)
                 ;; Enable completion and input history at the REPL.
                 ((module-ref module 'activate-colorized))))
              (else
               (display "Consider installing the 'guile-colorized' package
for a colorful Guile experience.\n\n"))))
##########

When I remove this file and try to connect again, the "No prompt  found!" error disappears, and the prompt looks normal.


## System information

$ guix describe
Generation 1	May 06 2019 11:29:00	(current)
  guix d6a68e9
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: d6a68e90483b35bdc2ea78afe2c81873be67ec95

I'm using Emacs 26.2, Geiser 0.10, and Guile 2.2.4, all installed as Guix packages.


---
https://sirgazil.bitbucket.io/

Message #8 received at 35727 <at> debbugs.gnu.org (full text, mbox):

From: Luis Felipe <luis.felipe.la <at> protonmail.com>
To: "35727 <at> debbugs.gnu.org" <35727 <at> debbugs.gnu.org>
Subject: Connecting Geiser to Guile listening to a socket: No prompt found!
 (.guile to blame)
Date: Tue, 08 Dec 2020 16:45:23 +0000

Hi, just to comment that this bug persists in the Guix System I'm using, with:

guix 08d8c2d
guile 3.0.4
emacs 27.1
geiser 0.12

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mekeor Melire <mekeor <at> posteo.de>
To: 35727 <at> debbugs.gnu.org
Cc: luis.felipe.la <at> protonmail.com, sirgazil <sirgazil <at> zoho.com>,
 bug-guix <at> gnu.org, acpadoanjr <at> yahoo.com.br
Subject: Re: bug#35727: Connecting Geiser to Guile listening to a socket: No
 prompt found! (.guile to blame)
Date: Mon, 12 Dec 2022 13:32:39 +0000

2019-05-14 06:17 sirgazil <at> zoho.com:

> I'm getting a "No prompt found!" error when I try to connect 
> Geiser to a Guile REPL like this:
>
> 1. In a terminal, run "$ guile --listen=/tmp/guile-socket"
> 2. In Emacs, "M-x geiser-connect-local", then "guile", and 
> finally "/tmp/guile-socket"
>
> When the Guile REPL start in Emacs, I get a "No prompt found!" 
> in the echo area, and the prompt in the REPL looks like this:
>
> https://multimedialib.files.wordpress.com/2019/05/emacs-geiser-guile-repl-no-prompt-found-2019-05-13.png
>
> After trying some things out with help from str1ngs on #guix, we 
> found out that the problem is related to the ".guile" file that 
> seems to be generated by the system by default. In my case, 
> ".guile" looks like this:
>
> ##########
> (cond ((false-if-exception (resolve-interface '(ice-9 
> readline)))
>        =>
>        (lambda (module)
>          ;; Enable completion and input history at the REPL.
>          ((module-ref module 'activate-readline))))
>       (else
>        (display "Consider installing the 'guile-readline' 
>        package for
> convenient interactive line editing and input history.\n\n")))
>
>       (unless (getenv "INSIDE_EMACS")
>         (cond ((false-if-exception (resolve-interface '(ice-9 
>         colorized)))
>                =>
>                (lambda (module)
>                  ;; Enable completion and input history at the 
>                  REPL.
>                  ((module-ref module 'activate-colorized))))
>               (else
>                (display "Consider installing the 
>                'guile-colorized' package
> for a colorful Guile experience.\n\n"))))
> ##########
>
> When I remove this file and try to connect again, the "No prompt 
> found!" error disappears, and the prompt looks normal.

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.

Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Antonio Carlos Padoan Junior <acpadoanjr <at> yahoo.com.br>
To: Mekeor Melire <mekeor <at> posteo.de>
Cc: 35727 <at> debbugs.gnu.org, luis.felipe.la <at> protonmail.com,
 sirgazil <sirgazil <at> zoho.com>, bug-guix <at> gnu.org
Subject: Re: 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

Mekeor Melire <mekeor <at> 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

Message #23 received at 35727 <at> debbugs.gnu.org (full text, mbox):

From: Luis Felipe <luis.felipe.la <at> protonmail.com>
To: Mekeor Melire <mekeor <at> posteo.de>
Cc: 35727 <at> debbugs.gnu.org, sirgazil <sirgazil <at> zoho.com>, bug-guix <at> gnu.org,
 acpadoanjr <at> yahoo.com.br
Subject: Re: bug#35727: Connecting Geiser to Guile listening to a socket: No
 prompt found! (.guile to blame)
Date: Thu, 12 Jan 2023 17:32:39 +0000

[Message part 1 (text/plain, inline)]

Hi Mekeor,

On Monday, December 12th, 2022 at 13:32, Mekeor Melire <mekeor <at> posteo.de> wrote:

> Does it work when you start the Guile REPL with an
> environment-variable called INSIDE_EMACS?

It does, thanks.


> 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.

I'm not sure what would be the right place to document that tho...

> Personally, I think this is only a bug in Geiser which should be
> able to parse colored prompts.

I just reported this to Geiser:

https://gitlab.com/emacs-geiser/guile/-/issues/26

So I think I'll close this issue.

[publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc (application/pgp-keys, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Message #29 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Luis Felipe <luis.felipe.la <at> protonmail.com>
To: Luis Felipe <luis.felipe.la <at> protonmail.com>
Cc: Mekeor Melire <mekeor <at> posteo.de>, 35727 <at> debbugs.gnu.org,
 sirgazil <sirgazil <at> zoho.com>, bug-guix <at> gnu.org, acpadoanjr <at> yahoo.com.br
Subject: Re: bug#35727: Connecting Geiser to Guile listening to a socket: No
 prompt found! (.guile to blame)
Date: Thu, 12 Jan 2023 19:20:14 +0000

[Message part 1 (text/plain, inline)]

On Thursday, January 12th, 2023 at 17:32, Luis Felipe <luis.felipe.la <at> protonmail.com> wrote:

> Hi Mekeor,
> 

> On Monday, December 12th, 2022 at 13:32, Mekeor Melire mekeor <at> posteo.de wrote:
> 

> > Does it work when you start the Guile REPL with an
> > environment-variable called INSIDE_EMACS?
> 

> 

> It does, thanks.
> 

> > 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.
> 

> I'm not sure what would be the right place to document that tho...
> 

> > Personally, I think this is only a bug in Geiser which should be
> > able to parse colored prompts.

Well, it turns out it is not:

«geiser guile is intended to work without extra .guile settings. my guess is that your .guile is possibly altering the looks of the prompt, that is explicitly not supported by geiser.» — jaor, https://gitlab.com/emacs-geiser/guile/-/issues/26

[publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc (application/pgp-keys, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Previous Next

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