-
Notifications
You must be signed in to change notification settings - Fork 342
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
Haskell process command errored with: (error "Unexpected response from haskell process.") #1496
Comments
I just upgraded to GHC 8.2.1 and suddenly I'm getting this, too. My project builds fine (no stack involved), but emacs mode is broken - EDIT: Downgrading to GHC 8.0.2 causes this error to go away. |
This is related: #1168 |
The issue was solved for me when I |
Where are you setting this? I tried entering |
This error message might be a common message for different class of errors(I am not sure about this). |
Hmm. In my case I don't think it's a package: I get it even on the default "Hello world" file generated by |
This is a duplicate of #1553. |
I am confronted to this message. How can we debug that to get more information on what's failing ? |
@nrolland This seems like a common catch all error clause whose occurrence entirely depends on the code that you are trying to load. Like mentioned above my issue was solved by setting I faced the same warning when I was trying to load a program with unlifted types. So you would have to produce a snippet of the program you are trying to load to debug it. |
@Abhiroop yeah, and since it's generic I imagined there was some "debug" facility to get more info to activate somewhere. There is an How did you come up with your idea of setting |
For potential future references, there seems to be a bunch of heuristics in Replacing the function
and
This was probably intended to match
Notice "one" in the response VS "1" in the match |
I'm seeing this issue on ghc 8.4.3 with the latest version of haskell-mode, without stack. haskell-process-log shows:
The issue seems to be that the code is using ":set prompt2" instead of :set prompt-cont as adamse points out in #1569. This can be verified in ghci:
I changed the code to set prompt-cont rather than prompt2 which got rid of the error above but does not seem to fix the reported issue although the error message seems irrelevant as the code does get loaded (which may even have been true before I made that change in the .el files on my machine). This issue seems like it is being fixed in #1605 |
A Haskell project which builds fine with
stack build
runs into this issue.No helpful error messages to debug too.
The text was updated successfully, but these errors were encountered: