3 ms·
Yep, though a feature request I've put in is to respond to a ctl-c by producing the results from the stream so far... that way if it's taking a while on a large
by avibryant 14y ago
Yep, though a feature request I've put in is to respond to a ctl-c by producing the results from the stream so far... that way if it's taking a while on a large file you can interrupt and still get something useful.
- deleted 14y ago[deleted]
- cgs1019 14y agoThis breaks ctl-c in my opinion. When I ctl-c I want shit to stop, not dump (potentially large quantities of) output into my terminal.
- wodow 14y agoIt could accept another signal (e.g. SIGUSR1) and have this clearly documented.
- neilk 14y agoI just added the SIGUSR1 feature to my hacky perl script (see my other comment). e.g. $ (while true; do cat /usr/share/dict/words; done;) | ./randline 3 & [2] 93937 $ kill -s SIGUSR1 93937 declinograph brotheler woolpack $ kill -s SIGUSR1 93937 lustrify brotheler bromophenol