[chuck-users] chuck --probe output: not stdout

[mike clemow]

Brian,

To err is human...  but to really screw things up, code it in ChucK.   ;)

Ah, okay.  Well, that at least provides me a good plan of action.  And I
never knew about the &> operator on the command line, so thanks for that!
 I suppose that "chuck --probe 2> output" would work as well.

Cheers,
Mike



http://michaelclemow.com
http://semiotech.org



On Thu, Feb 28, 2013 at 10:43 AM, Brian Sorahan <bsorahan at haivision.com>wrote:

> Hi Mike,
>
> It looks like the output of chuck --probe goes to stderr.
>
> You can see the difference with
> $ chuck --probe >probe.out
> and
> $ chuck --probe &>probe.out
>
> Cheers,
> Brian
>
>
> On Thu, Feb 28, 2013 at 8:06 AM, mike clemow <michaelclemow at gmail.com>wrote:
>
>> Hi Chuckists,
>>
>> system: mac 10.7.3, chuck 1.3.1.3 (64 bit)
>>
>> So, when I type `chuck --probe` I get the usual output to the console.
>>  Now, this has always been the case, however, I'm just now asking about it;
>> chuck does not seem to be sending that output to stdout.  I can't access it
>> that way.  In fact, if I want it in a file, I have to use script.
>>
>> Where is that console output going?  Why is it not going to stdout?
>>
>> Sorry if this question has been answered before.
>>
>> Best,
>> Mike
>>
>> http://michaelclemow.com
>> http://semiotech.org
>>
>>
>> _______________________________________________
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>>
>>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20130228/fa4ad817/attachment.html>