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

[vale981]

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]

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]

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]

me too. problem...

[ekaschalk]

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]

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

[ekaschalk]

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

[alexeiz]

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.

[swapneils]

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]

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

[allison-casey]

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

[gehrman]

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]

Are you all also running this on windows?

[swapneils]

@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]

Try running hy on git bash. It never showed the input prompt for me. Then try running hy on cmd. That worked, I got the input prompt Same thing happened on the *hy internal* buffer, even after I tried forcing emacs to use cmd. I moved a lot of my work onto wsl and do emacs on it through xlaunch and i3wm. I'll see if I get the same bug running emacs on its home planet.

…

On Sun, Dec 1, 2024, 7:19 PM Swapneil Singh ***@***.***> wrote: @riatzukiza <https://github.com/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 <#103 (comment)>. — Reply to this email directly, view it on GitHub <#85 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACROVPNI4UY72PGXVTC7XE32DO7UFAVCNFSM6AAAAABSHIGKYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGQZDGOJUGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>