[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KProcess and stdout/stderr!
From:       Waldo Bastian <bastian () kde ! org>
Date:       2001-10-30 21:17:10
[Download RAW message or body]

On Tuesday 30 October 2001 12:20 pm, Tim Lee wrote:
> On Monday 29 October 2001 06:44 pm, Waldo Bastian wrote:
> > On Monday 29 October 2001 02:17 pm, Tim Lee wrote:
> > > The binary is provided by a third party (Cisco VPN Client) that
> > > I am writting a KDE interface for.  Cisco only provides a binary
> > > so I can't do the setbuf.
> >
> > My man-pages says:
> >        If a  stream  refers
> >        to a terminal (as stdout normally does) it is line buffered.  The
> >        standard error stream stderr is always unbuffered by default.
> >
> > So to get stdout line-buffered by default, you will have to make it a
> > terminal. You may want to look at kdebase/konsole/.../TEPty.*
> > for how to setup a terminal.
> >
> > Especially
> > TEPty::setupCommunication(Communication comm)
> > and
> > int TEPty::commSetupDoneC()
>
> Thanks Waldo and others who have pointed me in correct
> direction on this.  I ended up inheriting from KProcess
> and using kdelibs/kdesu/kdesu_pty.h (libkdesu) to make
> a KProcessPty that does all the IO through a terminal.
> Seems to work well.
>
> Is anyone else interested in such a class?

Might be a good candidate for kdecore, or maybe we can integrate it with 
KProcess and add a flag "use Pty" ?

Cheers,
Waldo
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]