First, thanks to all who answered. I now have a partial solution to my problem.
On Friday 14 March 2003 02:23, Omer Zak wrote: > If Shlomo uses X-Window, then he can have his script write its stuff to a > file. > Then in another window, he can run: > tail -f script-output-file > and in a third window, he can run: > tail -f script-output-file | grep whatever\.\*pattern This is a fascinating idea and I'll save it for future use, even though it only partially solves my problem. I'll explain why partially at the end of this message. BTW - window #3 is not needed. Since I need the output of GREP to make a decision in the script (running in window #1), I just added a line to the script to cat the entire script-output-file to GREP after the line that creates the output. > On Thu, 13 Mar 2003, Alex Chudnovsky wrote: > > On Thursday 13 March 2003 23:11, shlomo solomon wrote: > > Use "tee". Kludge but works. In theory, this is exactly what I was looking for (but didn't know it existed). And it's even simpler than the above solution. So what's my problem? It seems that both the above solutions are writing to a buffer and the actual screen output is not immediate, but in spurts. Let me make that clearer. The original script creates a few hundred lines of output that would normaly (if not for the pipe and GREP) scroll **gently** off the screen during the few minutes it runs. But with both the above solutions, I get nothing on screen at first. After a little while, about 100 lines scroll at high speed and a while later, another 100, etc. This is certainly better than not having any output, but what I really wanted was to see the output as it's created. Again, thanks for all the ideas. -- Shlomo Solomon http://come.to/shlomo.solomon Sent by KMail (KDE 3.0.5a) on LINUX Mandrake 9.0 ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
