Please see the reply from Mike. So is your change ok here, I didn't fully understand about "There is also blocking with processing events - which is what I introduced." BFN, Don. ---------- Forwarded Message ---------- Subject: Re: kdenetwork/kmail Date: Sun, 15 Apr 2001 15:41:04 -0400 From: Mike Pilone To: Don Sanders Yes, At least for my use. I use the precommand to setup an ssh tunnel, then do all my pop checking through the tunnel, to ensure encrypted passwords. The tunnel must be established before kmail continues. It might be useful (if possible) to put the precommand in a seperate thread so the GUI updates, but prevent kmail from trying to connect to a host before the tunnel is established. I can write up a quick article about the ssh tunneling if it would help anyone. -mike On Sunday 15 April 2001 09:20 am, you wrote: > Hi, > > Sorry to interrupt. > > IIRC you implemented the precommand feature. I suspect that making the > execution of the precommand non-blocking may have undesirable side effects. > Is that correct? > > On Saturday 14 April 2001 22:09, Daniel Naber wrote: > > On Saturday 14 April 2001 20:50, CVS by coolo wrote: > > > don't block the GUI while waiting for the precommand to finish. > > > > Mhh, no blocking GUI = no blocking kmail, I guess. Are you sure this > > doesn't break people's configuration? Some people might use a command > > that needs to finish before fetching of the mail starts (that's just a > > guess, I don't use that option). > > I am concerned about this also. > > BFN, > Don. -- -- Mike Pilone Computer Scientist mpilone@slac.com http://www.slac.com/~mpilone/ ------------------------------------------------------- _______________________________________________ Kmail Developers mailing list Kmail@master.kde.org http://master.kde.org/mailman/listinfo/kmail