Re: dealing with verbose programs

2007-09-05 Thread Bruno Haible
Jim Meyering wrote: > 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. Incremental diffs would be cool... until then, here's m

Re: dealing with verbose programs

2007-09-05 Thread Jim Meyering
Ben Pfaff <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: >> Ben Pfaff <[EMAIL PROTECTED]> wrote: >>> Jim Meyering <[EMAIL PROTECTED]> writes: 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

Re: dealing with verbose programs

2007-09-05 Thread Ben Pfaff
Jim Meyering <[EMAIL PROTECTED]> writes: > Ben Pfaff <[EMAIL PROTECTED]> wrote: >> Jim Meyering <[EMAIL PROTECTED]> writes: >>> 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

Re: dealing with verbose programs

2007-09-05 Thread Jim Meyering
Ben Pfaff <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: >> 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 progres

Re: dealing with verbose programs

2007-09-05 Thread Ben Pfaff
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 rea

Re: dealing with verbose programs

2007-09-04 Thread Jim Meyering
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 w

Re: dealing with verbose programs (was: Re: new module 'calloc-posix')

2007-09-04 Thread Bruno Haible
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