-
Notifications
You must be signed in to change notification settings - Fork 689
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
cabal-install head ignores sigint (ctr+c) but responds to sigsusp (ctrl+z), sometimes (don't have a reproducable test case yet) #1345
Comments
Probably happens when we're reinstalling dependencies. This is the same behaviour that |
It may also be due to the fact that we're using System.Process API that does not do let us do ctl-c handling correctly yet. The old System.Cmd.system did this right, but that feature has been hard to expose with the more flexible System.Process API. There's a ghc ticket on this if someone wants to work on it. |
I wonder whether this has been fixed by #1448. |
Yes, #1448 strikes again. This is super annoying. How come that it returned? |
I just tested this issue with Cabal 1.22.0. Results:
@gracjan I responded to your comment on #1448. It would help to get some more info on that ticket since I can't reproduce the issue you mentioned with a current cabal. In the meantime, @cartazio it seems like the issue in this ticket has probably been resolved, since I can kill cabal with Ctrl-C during builds and installs on a recent version. Would you mind closing this ticket unless this is something you're still experiencing? Thanks a lot! |
It likely depends on the version of |
Optimistically closing. |
i'm testing out using cabal-install head (head as of now, so hash 2f32275) sandboxing, and i've had an instance of ctrl+c not killing cabal in a sandboxed build, but ctrl+z suspending it correctly
(still trying to figure out how to reproduce this problem though, so this may be a useless ticket if i cant reproduce )
The text was updated successfully, but these errors were encountered: