-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
(slurp *in*) can't be interrupted #2317
Comments
I would like to contribute a bit to CIDER but I have no idea where to start with this issue. Could you/someone give me some pointers? |
@TimoFreiberg I made a few articles about how to start debugging and contributing: http://hackingcider.com/ (particularly setting up CIDER for development ) Also, feel free to chat in #cider on the Clojure slack |
There's also http://docs.cider.mx/en/latest/hacking_on_cider/ |
thanks @dpsutton! The problem seems to be:
Possible solutions seem to be:
I'll try that approach, feedback appreciated :) |
Excellent research! Yeah, I think we should do both.
Btw, I'm not quite sure about this. Why is it correct to always add a final newline? |
Otherwise it would be impossible to enter an empty line into stdin |
You can just use |
Happy to hear that :) |
You can see here how to tweak the minibuffer setup for stdin https://github.com/clojure-emacs/cider/blob/master/cider-common.el#L87 |
Btw, if you're the mood for more detective/bug fixing I can suggest 2 more small issues that are somewhat related:
|
I'll take a look 👍 |
Current status: https://gist.github.com/TimoFreiberg/34d7efa24f2966daff44601ce6c4753e#file-nrepl-exception There's a problem though: calling |
Probably you're right. Not sure where would be best to handle this. Btw, I'm curious if we can somehow add a way to conclude the input read by the minibuffer with EOF (e.g. with some keybinding) to prevent the need to send a second "termination" message. |
Oh, actually it's quite obvious. Yeah I've been thinking about that as well. |
Well, improving things in nREPL is certainly doable now https://github.com/nrepl/nrepl/ CIDER will switch to using the new nREPL server pretty soon. |
Anyways, for now we should probably go with a termination message, until the transition to the "new" nREPL is completed. |
I've got it now. So we accept that users can close the nREPL stdin and maybe fix/improve that in the new nREPL project? |
Just for now.
We should certainly fix this there, my point was mainly that some people will keep using the legacy project for a while, so ideally we have to be compatible with it as well. CIDER will stop supporting the legacy nREPL as soon as I find some time to focus on this. :-) |
Add handler for the `quit` signal which sends an empty message to nREPL Add C-c C-c binding for `abort-recursive-edit` (which sends a `quit` signal)
Add handler for the `quit` signal which sends an empty message to nREPL Add C-c C-c binding for `abort-recursive-edit` (which sends a `quit` signal)
This is just creating a ticket for https://stackoverflow.com/questions/50493580/cider-for-emacs-stdin
It seems that slurping from the stdin right now can't be interrupted, which should certainly be possible.
The text was updated successfully, but these errors were encountered: