[chuck-users] chuck --probe output: not stdout
michaelclemow at gmail.com
Thu Feb 28 11:55:44 EST 2013
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.
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
> $ chuck --probe &>probe.out
> On Thu, Feb 28, 2013 at 8:06 AM, mike clemow <michaelclemow at gmail.com>wrote:
>> Hi Chuckists,
>> system: mac 10.7.3, chuck 126.96.36.199 (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.
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chuck-users