Michael Tsai on Twitter: "@czechboy0 But note that you can get NSTaskDidTerminateNotification before the last NSFileHandleReadCompletionNotification…"

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

honza dvorsky ‏@czechboy0 15 May 2015

Run Terminal Scripts from Swift in your Mac app — honza dvorsky http://honzadvorsky.com/blog/2015/5/14/run-terminal-scripts-from-swift-in-a-mac-app …
Michael Tsai ‏@mjtsai 15 May 2015

@czechboy0 Looks like this doesn't handle the case where the task never terminates because the output pipe buffer gets filled up.
honza dvorsky ‏@czechboy0 15 May 2015

@mjtsai Good point. How could I do that? The buffer limit is 65536 bytes (OS X pipe buffer size), not sure what happens if overflown :)
Michael Tsai ‏@mjtsai 15 May 2015

@czechboy0 Build up the output/error data a chunk at a time. Don't -waitUntilExit. Keep running the run loop until file handles are empty.
honza dvorsky ‏@czechboy0 15 May 2015

@mjtsai But what if the script isn't outputting anything for a while? Wouldn't that terminate before the script itself does?
Michael Tsai ‏@mjtsai 15 May 2015

@czechboy0 No, because instead of calling -waitUntilExit you run your own loop until the output and error are finished.
honza dvorsky ‏@czechboy0 15 May 2015

@mjtsai And those are guaranteed to only finish when the whole script has terminated?

‏@mjtsai

@czechboy0 But note that you can get NSTaskDidTerminateNotification before the last NSFileHandleReadCompletionNotification…

9:16 AM - 15 May 2015

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.