Re: Capture console app output into texview?

2009-11-21 Thread Till Harbaum / Lists
Hi, thanks again for that hint. Unfortunately adding /* switch to line buffered mode */ if(setvbuf(fh, NULL, _IOLBF, 0)) perror(setvbuf(_IOLBF)); to the program posted by Dov doesn't change anything. Are there limitations on changing the buffer mode? E.g. only

Re: Capture console app output into texview?

2009-11-21 Thread David Nečas
On Sat, Nov 21, 2009 at 09:39:49AM +0100, Till Harbaum / Lists wrote: thanks again for that hint. Unfortunately adding /* switch to line buffered mode */ if(setvbuf(fh, NULL, _IOLBF, 0)) perror(setvbuf(_IOLBF)); to the program posted by Dov doesn't change

Re: Capture console app output into texview?

2009-11-21 Thread Artur Galjamov
Hi, After exec(), child clib's startup routine determines buffering mode for stdout (i.e. calls fdopen(1, w+)). You can setup pseudo-terminal instead of pipe, to make child's stdout line-buffered. optimistic snippet: = #include