Output is too verbose

[ndmitchell]

If you write one line per build thing, you get a wall of text. Do something like Ninja and have one line I keep reusing, at least as an option.

[ndmitchell]

Add a new verbosity setting, somewhere between Quiet and Normal - perhaps Compact? Then in that mode, any cmd call automatically turns on ignoring stdout and stderr. Any call to putNormal reuses the same line. Should be fairly easy to do.

[ghost]

:+1: for that. Can you put an option --Quiet-if-ok that only display the command name and no output if all is ok and command and stdout if an error ocurred?

[ndmitchell]

See https://groups.google.com/d/msg/shake-build-system/ZPyTIfVL-dA/JtBrCyJSAgAJ for a description and code of how to do it better, in particular with a video at https://asciinema.org/a/c7f3jybf7qwwt0i2lo6r02ifs. All from @nomeata.

[nomeata]

BTW, the video is of a run with -j 1, which is half as fun. But rest assured that even with -j 2 it does just what you would expect :-)

[ndmitchell]

I wrote a new mode --compact which follows more the style of Buck/Bazel. Picture at https://asciinema.org/a/228061

[nomeata]

Nice.

Sub-second-precision is a bit noisy (and silly when the view is updated every 0.1s+skew, or is that an asciicast artifact?). Maybe only show time after one second, and then rounded down to full seconds).

[ndmitchell]

Good suggestions: https://asciinema.org/a/228101

[nomeata]

That's better :-)

[dwijnand]

Add a new verbosity setting, somewhere between Quiet and Normal - perhaps Compact?

706 proposes, with Quiet and Normal renamed to Error and Info, the Warn level verbosity, which is reachable with one -q added.