-
Notifications
You must be signed in to change notification settings - Fork 347
Prompts to restart Haskell process after every character typed in an identifer #349
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
Comments
Does this sound like your issue? haskell/cabal#1715 |
My issue is that the emacs mode gets stuck in a bad state when cabal repl doesn't start properly. That issue is my most common reason for cabal repl not to start, but I doubt the annoying "ask again after every keystroke" behavior depends on exactly why the process isn't surviving. |
Do you get a "do you want to restart?" prompt after the error fails? |
Yes, I get the normal "do you want to restart?" prompt immediately after the failure as expected. Then whatever answer I gave, typing a letter at the end of an identifier brings up that same prompt again. |
Can you check with a blank config somewhere? I wonder if you've enabled an option somewhere that tries to automatically keep reloading your project every time you edit the file. |
Does #443 fix this? This may be due to the completion function starting after every character typed. If not, then maybe documentation function? |
After trying and failing to start a Haskell process, typing a character at the end of an identifer in the Haskell buffer prompts to restart again.
I have haskell-mode 13.10, GHC 7.8.3, cabal-install version 1.20.0.3 using version 1.20.0.2.
To reproduce, it's enough to make a trivial .cabal file for a Test.hs containing the line
After something like C-c C-l that tries to start a haskell process, the process will die with the log showing the compiler error message. After that, adding letters to the end of "main" will prompt to restart the process after each character typed.
The text was updated successfully, but these errors were encountered: