On Mon, Oct 01, 2001 at 01:00:37PM +0400, Alexander V. Lukyanov wrote: > > The only problem I know of is that I had to always enable "quiet" (-q) > > for cls, disabling status reports, due to overlap. I'm not sure how to fix > > this; it'd be very nice to have. (Perhaps a setting for FileCopy to > > tell it to go NoStatus once the source peer has started giving data?) > > Currently a parent job (CmdExec) tells child job to show status. There > is no option to clear status when the child wants to. Something should > be changed, I don't know yet what.
I experimented with this a bit. I tried making FileCopy mark when it started writing, and had CopyJob stop updating the status line when that happened. (Of course, this should only happen when it's writing to a FileCopyPeerFDStream pointing at stdout, but first things first ...) Unfortunately, the status line needs to be cleared, and that needs to happen before any writing to the terminal happens. Dead end on that idea. Any insights? This is complicated by the fact that these classes don't have access to the StatusLine except when actually updating it. We can't delay any output to the screen until the next time the status line would have been updated, obviously ... -- Glenn Maynard
