Kill compass
-
My first encounter with compass
$ compass watch >>> Compass is watching for changes. Press Ctrl-C to Stop. ^C^C^C^C^C^C^C^C^C^C^C^Z [1]+ Stopped compass watch $ kill %1Two seconds in and it's already left the impression of a compulsive liar on me. Fortunately for me I don't need it.
-
install instructions for compass...
# gem install compass
-
Two seconds in and it's already left the impression of a compulsive liar on me. Fortunately for me I don't need it.
What? You pressed ^C, and it stopped.
-
Looks like it didn't stop until he pressed ^Z.
-
It didn't stop for Ctrl-C/
SIGINT. He had to background the process then send it aSIGKILLto stop it.
-
Ok, look, since you guys didn't get it, he pressed ^C, and then some other stuff happened, and then it stopped.
I simplified my recap the first time.
-
Correlation != Causation
-
post hoc ergo propter hoc
-
Most of us have no doubt actually seen lots of applications where ^C would eventually work--they're usually in the middle of a loop and (in Windows terms) not processing events or something similar.
-
Yep; however, there's worse.
[spoiler]
Namely,signal(SIGINT, SIG_IGN);
[/spoiler]
-
Namely,
signal(SIGINT, SIG_IGN);http://cdn.smosh.com/sites/default/files/bloguploads/simpsons-fire.gif
-
http://media.giphy.com/media/e1Lv6Gvd8bFFC/giphy.gif
http://cdn.smosh.com/sites/default/files/bloguploads/simpsons-fire.gif
Welp, that escalated quickly!
Filed Under: Not gonna insert meme-pictures here
-
well i wasn't going to set on fire when i was right next to it, no?
see the important part about killing it with fire is distance. you want to be close enough to be sure the job gets done but not so close you end up getting set on fire youreself.
-
you want to be close enough to be sure the job gets done but not so close you end up getting set on fire youreself.
Unless you're theHumanVulpine Torch ;)
-
The ruby part didn't bother me much. I have fond memories of ruby and in this case the system package manager did everything for me. I don't think I ever entrusted
gemwith root privileges.There are few tools where not exiting immediately on ^C is acceptable. Editors maybe? Giving explicit promise to follow conventions then misbehaving anyway may have comical value in certain circumstances and be therefore socially acceptable. I do however have extreme prejudice when a machine does it.
I wanted to confirm that it wouldn't stop even if I waited two hours
$ compass watch sh: compass: command not found $There, exits immediately. Must have been reflex debugging on my part.
