We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I'm not mistaken, canceling CTRL+c should produce no output like most/all other commands.
CTRL+c
Currently, this is what happens (on Ubuntu bash 4.2 at least, untested elsewhere) :
$ grep -ir 'foo' . | fpp ^CTraceback (most recent call last): File "/usr/local/PathPicker/src/processInput.py", line 144, in <module> doProgram() File "/usr/local/PathPicker/src/processInput.py", line 120, in doProgram lineObjs = getLineObjs() File "/usr/local/PathPicker/src/processInput.py", line 102, in getLineObjs inputLines = sys.stdin.readlines() KeyboardInterrupt Nothing to do! :D
The text was updated successfully, but these errors were encountered:
79b3d25
Stack overflow to the rescue: http://stackoverflow.com/questions/1112343/how-do-i-capture-sigint-in-python
haha :D that should fix the stacktrace spew, thanks @jdunk ! this was annoying me too, glad you filed. 🎉
Sorry, something went wrong.
@pcottle Nice, thanks! :)
No branches or pull requests
If I'm not mistaken, canceling
CTRL+c
should produce no output like most/all other commands.Currently, this is what happens (on Ubuntu bash 4.2 at least, untested elsewhere) :
The text was updated successfully, but these errors were encountered: