Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No prompt found or ‘comint-prompt-regexp’ not set properly #85

Open
vale981 opened this issue Oct 12, 2019 · 14 comments · May be fixed by #103
Open

No prompt found or ‘comint-prompt-regexp’ not set properly #85

vale981 opened this issue Oct 12, 2019 · 14 comments · May be fixed by #103

Comments

@vale981
Copy link

vale981 commented Oct 12, 2019

Hi,
When i run run-jedhy, i get the following error message:

hy-shell--redirect-check-prompt-regexp: No prompt found or ‘comint-prompt-regexp’ not set properly

A little digging around showed, that somehow the hy-shell--redirect-output-buffer is not created.

I am on Emacs 26.3.

@ekaschalk
Copy link
Collaborator

What version of Hy are you using?

After running it, is *Hy* buffer created/can you see the Hy process in list-processes? Also try manually sending text eg like (hy-shell--redirect-send "(setv x 1)") then running hy.

@vale981
Copy link
Author

vale981 commented Oct 13, 2019

Hi, thanks for replying.

I am using hy 0.17.0.

after running run-jedhy, list-processes shows:

Hy              4444    run     *Hy*            /dev/pts/3   hy --spy
Hy Internal     4408    run     *Hy Internal*   /dev/pts/2   hy
server          --      listen  --              --           (network server on /tmp/emacs1000/server)

(hy-shell--redirect-send "(setv x 1)") results in the same error as the above reported:

hy-shell--redirect-check-prompt-regexp: No prompt found or ‘comint-prompt-regexp’ not set properly

@PlumpMath
Copy link

me too. problem...

@ekaschalk
Copy link
Collaborator

I'm not sure when I will be able to get to this, my job has taken my open source time away.

PRs are welcome.

@vale981
Copy link
Author

vale981 commented Nov 13, 2019

I understand... My studies have taken mine as well.
I'll look into it, when I find time.

@ekaschalk
Copy link
Collaborator

Is anyone aware if this is actually still happening? From #93 it's not clear if this is still a thing.

@alexeiz
Copy link

alexeiz commented Aug 31, 2020

I have to remove the code line that produces this error to make hy-mode work for me. I believe the comint-prompt-regexp test is useless.

@jams2 jams2 linked a pull request Feb 7, 2021 that will close this issue
@swapneils
Copy link

Just want to note I ran into the same issue. I haven't tried implementing #103 or alexeiz's fix, though, so either may be valid solutions.

@Inc0n
Copy link

Inc0n commented Jan 10, 2022

Is there any update for this, for those of us would prefer avoiding manually installing these patch?

@allison-casey
Copy link

with alpha 4 out the door now, i'll see what i can do to get hy-mode back up to date

@gehrman
Copy link

gehrman commented Mar 30, 2024

I just ran into this, and manually applying #103 didn't appear to fix this. I'll try to get a PR up to fix this once I get a bit of time to try and dig in on what's happening.

FWIW, version information

Emacs 29.2

Package hy-mode is dependency.

     Status: Installed in ‘hy-mode-20211016.2011/’ (unsigned).
    Version: 20211016.2011
     Commit: df814865a1faa8414dacdbb35b2a9029995312ec
    Summary: Major mode for Hylang
   Requires: dash-2.18.0, s-1.11.0, emacs-24
    Website: https://github.com/hylang/hy-mode
   Keywords: languages lisp python 
Other versions: 20211016.2011 (melpa), 1.0.4 (melpa-stable).

@riatzukiza
Copy link

Are you all also running this on windows?

@swapneils
Copy link

swapneils commented Dec 2, 2024

@riatzukiza I was running on windows. Back when I was actively using hy I ran Emacs (and so any related applications) in Windows cmd rather than git bash, however, so not sure if it's the same issue you encountered.

@riatzukiza
Copy link

riatzukiza commented Dec 2, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants