> I know there was another cygwin user that had similar experiences.
> Is this a limited situation? Is anyone else seeing these kinds of issues?
Same problem since I updated to the new X.org 7.4: I have xwin
crashes. Also with XP and also using a vncclient (TightVNC)
This is how it happens:
- sud
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-file-
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
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 emulator (
Okay, I'm digging a little deeper, and I think that I have noticed some
things that might be helpful and I've created some files that might shed
some light.
The files below are output from what I'm running through xterm. Auto
indicates simulations in which the output was automatically teed to a f
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
I know there was another cygwin user that had similar experiences.
Is this a limited situation? Is anyone else seeing these kinds of issues?
Since I'm new here maybe this has been fixed and so it's no longer discussed?
I looked in the archives but maybe I missed something.
On Sat, 7 Feb 2009 19:
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 correctly,
the "| tee
I reported the exact same problem in my mail titled -
Bug: xinit: XWin Server shortcut won't work if Cygwin not in C:
I had a default HOME but installed Cygwin at d:\cygwin. Updating the "starts
in" field to "d:\" fixes the problem.
- Original Message
From: Simon McQueen
To: cygwin-x
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
12 matches
Mail list logo
