On Tuesday, December 9, 2014, Ken Thomases wrote:
> On Dec 9, 2014, at 8:24 AM, SevenBits > wrote:
>
> > Do you know how to trigger the automatic flushing of standard output
> like you described? There doesn't seem to be anything in NSTask to do it,
> though it probably wouldn't be there anyway.
On Dec 7, 2014, at 4:42 PM, Keary Suska wrote:
> On Dec 7, 2014, at 1:35 PM, SevenBits wrote:
>
>>>
>>> I don't know if this approach is more likely to work in a sandboxed app. I
>>> doubt it, because it would be an enormous hole in the sandbox. If you can
>>> direct Terminal to run arbit
On Dec 7, 2014, at 5:35 PM, SevenBits wrote:
> On Dec 7, 2014, at 4:03 PM, Ken Thomases wrote:
>>
>> Second, even using Launch Services isn't the best way to do this (sandbox
>> issues aside). It's better to run the equivalent of this AppleScript script:
>>
>> tell app "Terminal"
>> activa
On Dec 7, 2014, at 1:35 PM, SevenBits wrote:
>>
>> I don't know if this approach is more likely to work in a sandboxed app. I
>> doubt it, because it would be an enormous hole in the sandbox. If you can
>> direct Terminal to run arbitrary commands, what protection does the sandbox
>> provid
> On Dec 7, 2014, at 4:03 PM, Ken Thomases wrote:
>
> On Dec 7, 2014, at 2:29 PM, SevenBits wrote:
>
>> I have a sandboxed app destined for the Mac App Store. Inside of it is an
>> embedded console program which I want to open in Terminal (i.e Terminal.app
>> opens and the app runs in its wi
On Dec 7, 2014, at 2:29 PM, SevenBits wrote:
> I have a sandboxed app destined for the Mac App Store. Inside of it is an
> embedded console program which I want to open in Terminal (i.e Terminal.app
> opens and the app runs in its window). Here’s what I’m doing:
>
> NSString *interactiveExecut
