-
Notifications
You must be signed in to change notification settings - Fork 11
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
Emacs freezes on displaying docstring #9
Comments
That doesn't look like anything a timeout would mitigate. Looks like a crash inside nrepl, and not specific to When nrepl.el fires off a request, it's perfectly capable of detecting exceptions thrown in the code it sent. In the above case, nrepl itself has obviously crapped out and so the async "done" response never got to nrepl.el. FWIW, there was never any support in Slime for timeouts, because it was perfectly valid (if ill-advised) to execute a long-running synchronous command. |
A timeout might allow me to get control of Emacs back - rather than having to totally kill it and restart it (which seems to be my only option when it hangs like that). Do you know how we can get at the NPE? |
I agree that the timeout would help in this case, but if the backend is broken like this, then all bets are off. I believe that's why Slime never had any safeguards against implementation bugs in the swank backends. If I were trying to track down the NPE, I'd open up the source of one of the functions in the above stacktrace (e.g. |
Through a combination of nrepl.el updates and upgrading lein to the latest preview, this issue seems to have disappeared. Happy happy joy joy! |
Now I'm starting to see Emacs freeze on autocompleting stuff.
I see the following Clojure stacktrace, and Emacs hangs. I assume that Emacs is waiting for a reply from the Clojure process which isn't being received due to this error. If this is the case, perhaps it's worth looking into adding timeouts to the synchronous comms?
The text was updated successfully, but these errors were encountered: