Re: [Geiser-users] Help associating source and REPL - "No prompt found!"

[Jon Miller]

I did the same with run-geiser and eventually tracked it down to
geiser-racket--prompt-regexp. My racket prompt looks like:
Welcome to Racket v5.3.6.
>

So, I added the following to my startup:
(setq geiser-racket--prompt-regexp "^\\(\\(mzscheme\\|racket\\)@\\|\\)[^ ]*> ")

With that, the REPL starts and I can switch back and forth with C-c C-z. Next
up is seeing why it takes so long to send definitions over to the REPL via
C-c M-e (geiser-eval-definition-and-go). When I run that, I get a spinning
wheel for my cursor until 30s at which point I'm back to the REPL but the
definition didn't make it there with me. 

I'm hoping that situation is known and/or potentially related to how I've
modified the prompt regexp? If not, I'll take a look further a bit later in
the day. Need to get some other work done. :-)

-- 
Jon Miller

address@hidden writes:

> I really want to get this working, so I went ahead and launched edebug and
> here is my mediocre notes that I took during the session:
> ; Using edebug-defun on geiser-debug--send-region
> ;  gets stuck on (ret (geiser-eval--send/wait code))
> ;    looks like it is (geiser-eval--connection) that yields the missing REPL 
> connection message
> ;      that comes down to geiser-repl--connection which relies upon 
> geiser-repl--connection*
> ;        Looks like the assigned buffer name doesn't work. 
> (geiser-repl--set-up-repl geiser-impl--implementation) yield nil
> ;          Would have set impl to 'racket' had (geiser-repl--repl/impl impl) 
> returned non-nil
> ;            Within geiser-repl--repl/impl, geiser-repl--repls is nil and 
> repls isn't passed, so the dolist loops through nothing.
>
> I'm not sure if the variable geiser-repl--repls being set to nil is the key
> in this analysis or not, but it would appear so to me. I looked at it's
> initial definition but haven't yet see where it could be updated. 
>
> Perhaps I'll step through run-geiser after some lunch.