Jim Meyering <[EMAIL PROTECTED]> writes: > Bruno Haible <[EMAIL PROTECTED]> wrote: >> Karl Berry wrote: >>> A wild thought: what if gnulib-tool saved its output during a run, and >>> then presented a *diff* of the new output and the old output? I at >>> least would find that considerably more readable. >>> >>> (Along with a mention of the file where the full output can be found, of >>> course.) >> >> I'd love to have the same feature for "configure" and "make" runs. >> It could be a general-purpose utility, taking a command line as argument, >> like 'time' and 'nice' are. > > Ha! I wrote the following a few weeks ago, thinking some day > I'd write something more involved. I'm not very happy with it, > because, at least with coreutils, it runs for too long without > giving any progress indicator.
You could use "tee" to display the program's output as it runs, then append the diff when it has completed. -- "A computer is a state machine. Threads are for people who cant [sic] program state machines." --Alan Cox
