teddybouch wrote:
That's it! If I just throw some of the fflush commands in here and there in
strategic places, I get all the output I am looking for up to those
statements. Why would this be needed sometimes and not others?
It's always needed if you must have output at a particular point in th
That's it! If I just throw some of the fflush commands in here and there in
strategic places, I get all the output I am looking for up to those
statements. Why would this be needed sometimes and not others?
--
View this message in context:
http://www.nabble.com/Saving-all-xterm-output-to-a
teddybouch wrote:
Jon TURNEY wrote:
If you really want to prove this is an xterm issue (which seems unlikely
to me
as this really revolves about what bash is doing), you should compare the
behaviour between running the command under an xterm and running it under
some
other terminal emulato
wed by called to fflush(stdout) - might this have something to do
with it?
--
View this message in context:
http://www.nabble.com/Saving-all-xterm-output-to-a-file-tp21894608p21906148.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.
--
Unsubscribe info: http://
sure that this theory holds water, but I wanted to throw it
out there.
--
View this message in context:
http://www.nabble.com/Saving-all-xterm-output-to-a-file-tp21894608p21903611.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwi
teddybouch wrote:
Sorry, I'm not entirely sure I understood all that, but I wanted to give an
update. I wrote a script and ran over 250 tests over last night using this
syntax:
./run 1 Joiner default 2>&1 | tee 2_7_09_results.dat
Only one of these tests gave output. Mark, if I understand you co
opening it.
I'm not sure if this will cause problems, and since it was test #67 that
gave results last night, I don't think that would be the problem, but I'm
going to try just closing bash and xterm between runs today.
--
View this message in context:
http://www.na
On Sun, Feb 8, 2009 at 6:35 AM, Thomas Dickey wrote:
> hmm - yes (I had at hand a script which does the latter, and couldn't
> recall the detail needed for the former, which seemed to be what OP
> requested).
Redirects are processed left-to-right. So this:
command >foo 2>&1
says "send stdout i
On Sat, 7 Feb 2009, Gary Johnson wrote:
../run 1 Joiner default 2>&1 > results.dat
I think that has to be written this way:
../run 1 Joiner default > results.dat 2>&1
But if you (the OP) wants to see what's going into that file, you
should tee, like this:
../run 1 Joiner default 2>&1
e, so
I am assuming that it has to do with that. Any ideas?
--
View this message in context:
http://www.nabble.com/Saving-all-xterm-output-to-a-file-tp21894608p21896001.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubs
On 2009-02-07, Thomas Dickey wrote:
> On Sat, 7 Feb 2009, teddybouch wrote:
>
> >I am trying to automate a simulation process, and part of this involves
> >capturing the output that is written to an xterm window when a particular
> >process is run. I thought that I had this figured out using the f
On Sat, 7 Feb 2009, teddybouch wrote:
I am trying to automate a simulation process, and part of this involves
capturing the output that is written to an xterm window when a particular
process is run. I thought that I had this figured out using the following
command:
../run 1 Joiner default > re
t that ought to be
there. Now, it has progressed to the point that I'm not getting any of the
printout statements at all - they don't appear in the xterm window or in the
file.
What do I need to do to get this to work? Thanks very much for your help.
Andrew Bouchard
--
View this message
13 matches
Mail list logo
