That is true in bash shells, but tcl isn't bash. I actually saw this on the tcl wiki and thought it to be strange.
Apparently, what 2>@ does in the tcl pipe is to direct stderr to the stdout of the program. To send both in bash, I always do this: someprog 2>&1 or to send it to a file: someprog > ofile 2>& But tcl isn't bash. That doesn't mean it won't work - please let me know what actually works and I will put a blurb on the web page about it for those who need this. - Don On Mon, 2007-03-26 at 16:13 -0400, Chris Fant wrote: > I remember it as > > ./myProg 2>&1 > > to send myProg's stderr to stdout. > > On 3/26/07, Don Dailey <[EMAIL PROTECTED]> wrote: > > My people have asked about sending stderr to the display when > > running the cgos tcl client. Several people on CGOS use the > > perl client because of this. > > > > I think it can be done by appending "2>@ stdout" to the > > command line invocation of your program. At least in linux. > > > > here is an example bash script to run a hypothetical program > > called MyBot while send stdout to the display (as well as the > > cgos client information messages: > > > > > > ------------------[ runBot script ]-------------------------- > > > > #!/usr/bin/bash > > > > ./cgos3-64 MyBot-1.0 aPassWord "./MyBot -l 10 2>@ stdout" stopMyBot > > > > > > > > > > _______________________________________________ > > computer-go mailing list > > [email protected] > > http://www.computer-go.org/mailman/listinfo/computer-go/ > > > _______________________________________________ > computer-go mailing list > [email protected] > http://www.computer-go.org/mailman/listinfo/computer-go/ _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
