Re: Coproc usage ... not understanding

2011-08-10 Thread Greg Wooledge
On Wed, Aug 10, 2011 at 10:07:20AM -0600, Bob Proulx wrote: > The unbuffer expect script sets up a tty around the called program so > that instead of a pipe the program detects a tty. > The stdbuf utility works by setting up an LD_PRELOAD library > libstdbuf.so that replaces the libc calls and int

Re: Coproc usage ... not understanding

2011-08-10 Thread Bob Proulx
Greg Wooledge wrote: > Linda Walsh wrote: > > Bob Proulx wrote: > > >This may be a good point to mention this reference: > > > > > > http://www.pixelbeat.org/programming/stdio_buffering/ > > > Does it only work with gnu programs? I.e. how would they know to > > not buffer > > Sounds l

Re: Coproc usage ... not understanding

2011-08-10 Thread Greg Wooledge
On Tue, Aug 09, 2011 at 05:47:09PM -0700, Linda Walsh wrote: > Bob Proulx wrote: > >This may be a good point to mention this reference: > > > > http://www.pixelbeat.org/programming/stdio_buffering/ > Does it only work with gnu programs? I.e. how would they know to > not buffer Sou

Re: Coproc usage ... not understanding

2011-08-09 Thread Linda Walsh
Chet Ramey wrote: On 8/9/11 8:19 PM, Linda Walsh wrote: Linda Walsh wrote: I did think of that...but I thought when the foreground process closes 'input', then all of the chained utils should see 'eof', and should then flush their output...at least that was my belief in how they "should"

Re: Coproc usage ... not understanding

2011-08-09 Thread Chet Ramey
On 8/9/11 8:19 PM, Linda Walsh wrote: > Linda Walsh wrote: >> I did think of that...but I thought when the foreground >> process closes 'input', then all of the chained utils should see 'eof', and >> should then flush their output...at least that was my belief in how they >> "should" be working

Re: Coproc usage ... not understanding

2011-08-09 Thread Linda Walsh
Bob Proulx wrote: Chet Ramey wrote: Linda Walsh wrote: Ideas? You're probably running into grep (and sort, and sed) buffering its output. I haven't been able to figure out a way past that. This may be a good point to mention this reference: http://www.pixelbeat.org/programming/stdio_bu

Re: Coproc usage ... not understanding

2011-08-09 Thread Bob Proulx
Chet Ramey wrote: > Linda Walsh wrote: > > Ideas? > > You're probably running into grep (and sort, and sed) buffering its > output. I haven't been able to figure out a way past that. This may be a good point to mention this reference: http://www.pixelbeat.org/programming/stdio_buffering/ And

Re: Coproc usage ... not understanding

2011-08-09 Thread Linda Walsh
Linda Walsh wrote: I did think of that...but I thought when the foreground process closes 'input', then all of the chained utils should see 'eof', and should then flush their output...at least that was my belief in how they "should" be working...(sigh)... --- Um...that got me to thin

Re: Coproc usage ... not understanding

2011-08-09 Thread Linda Walsh
Chet Ramey wrote: What am I doing wrong? You're probably running into grep (and sort, and sed) buffering its output. I haven't been able to figure out a way past that. Chet --- I did think of that...but I thought when the foreground process closes 'input', then all of the chained ut

Re: Coproc usage ... not understanding

2011-08-09 Thread Chet Ramey
On 8/3/11 4:11 PM, Linda Walsh wrote: > I've searched for coproc usage examples on the web, but there aren't > many, and the few I found, while working for their test case, didn't > fully replicate my setup, so it didn't work. > > > Ideas? > > > What am I doing wrong? You're probably running

Re: Coproc usage ... not understanding

2011-08-03 Thread Linda Walsh
I could do the whole thing in perl as well. Part of my reluctance to do that, is I wanted to learn why coproc wasn't working, and how to make it work. If I only use 'old skills', how will I learn anything new? Andreas Schwab wrote: awk would be much better suited for this task. Andreas.

Re: Coproc usage ... not understanding

2011-08-03 Thread Andreas Schwab
awk would be much better suited for this task. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."