Closed Gr3q closed 4 years ago
Sorry for the slow response. I think I was expecting people to input 'no' instead of 'ctrl+c'. I will take a look at this since I expect there are a number of places where the program doesn't exit cleanly.
This has not been forgotten! This will be fixed in the full release which hopefully will be in the next week or two.
This feature is now present in the latest release
Describe the Bug:\ App does not handle KeyboardInterrupts too nicely. Not an urgent matter
Output of Command It looks like this
Machine (please fill in the following information):
To Reproduce Steps to reproduce the behavior:
Expected behavior Exit without errors