On Tuesday May 05 2015 14:23:50 René J.V. Bertin wrote: Actually ...
>... The alternative would be to do the tcl equivalent of `if( isatty(stdout) >)` because the flush probably makes sense only when stdout is connected to a >terminal ... How often is this flush executed, and what percentage of the corresponding progress indication is never sent to a terminal? Flushing can be expensive (very, even), and *could* be part of what delays build/upgrade commands for ports that have a lot of dependencies (the VM in question takes almost a minute to check all dependencies of port:kde4-workspace before it starts fetching/extracting/patching/etc). R. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
