Herold Heiko <[EMAIL PROTECTED]> writes: > With the new spiffy real time progress bar it's rather nice to see > in real time the progress :-)
Thanks. That's one reason I've now made the default -- so that even the people who don't normally play with the options get to see it at least. > On the other hand often it is usefull to have a logfile, too. > > Now however it is not anymore "the same" redirecting always to a > logfile and doing tail -f in order to having both, since this means > no progress bar. I've always considered the real-time progress and the log to be an either-or thing. I suppose the code could still work by instantiating too progress bars, but I've never thought of the need for that. Do you know of other programs that support two simultaneous output modes? Also note that you can still save the "bar" output to the log file, although it won't be pretty. > Would it be to difficult / complex to implement a possibility of > double output, one to screen (possibly on progress bar mode), > another to the logfile (always in dot mode) ? Not too complex, but it does sound like a needless complexity. > also, I beg pardon for the question, it's late and I won't touch > this anymore till tomorrow... I'm looking into the current cvs on > windows, if wget is printing on the screen in bar mode, is it > supposed to continue in bar mode if send it to bg with ctrl-break / > sighup, creating an awfull mess ? Or should it / does it currently, > on unix, revert automatically to dot mode if put in bg ? It doesn't, because I didn't think of it. The progress bar code doesn't yet support such "conversion" of one progress bar to the other. What it could do is entirely turn off logging. Or maybe the conversion could be hacked in... but that might be ugly to code. Different progress bars would want to keep different kind of bookkeeping information. I'll have to think about this some more.
