From: hlu@phys1.physics.wsu.edu (Hongjiu Lu) Subject: Re: Good comm program? Date: 21 Jul 1992 23:50:57 GMT
In article <9207201343@myamig2.myamiga.mixcom.com>, smp@myamig2.myamiga.mixcom.com (Steve Palm) writes:
|> arumble@extro.ucc.su.OZ.AU (Anthony Rumble) writes:
|> :
|> : If *SOMONE* could post a *GOOD* port of Minicom (One that works) we
|> : might just have a good Comms package..
|>
|> Before I post . . .
|>
|> I have Minicom working just great. It only has ONE problem on my system.
|>
|> For up/downloads, it opens a window to show status. It's opening a pipe
|> to capture the output of the transfer command, and sending that to the
|> input of the window...
|>
|> Are pipes buffered? Because output to that window is only updated after
|> quite some stuff has flowed through, making it useless as a status box.
|>
If you use stdio, I believe everything is buffered by default. You can use
1. setbuf (fp, NULL);
2. setbuffer (fp, NULL, 0);
3. setvbuf (fp, NULL, _IONBF, 0);
to turn off the buffering for status window. Pick one you like.
|> If this doesn't bother anyone, I'll put it up somewhere.
-- H.J. Gcc/libc maintainer for Linux.