Support quiet output

[tari]

A -Q command line option or something to suppress some output would be helpful for scripting; in particular the "Pass one..." messages and such.

I have some code that's running spasm as a subprocess, and without a way to turn those messages off I can't easily ensure I only get my own code's output.

[Eeems]

Can't you just pipe the output to /dev/null?

[tari]

Not easily and portably! (It's not a shell script and it needs to run on platforms that aren't unixy.)

[Eeems]

I'd be interested to know what language you are using for this that doesn't have the ability to easily capture subprocess output in a portable mechanism.

[tari]

It's not that I can't capture output, but I don't care about it so don't want to capture it. (I'm using Rust.)

[calc84maniac]

Does .stdout(Stdio::null()) not work?

[tari]

It does; I managed to overlook it? Though I recall I wanted to redirect stdout to stderr so that output could still appear as well.

In any case a "quiet" flag still seems generally useful.

[alberthdev]

Not opposed to adding this feature - I think this would mainly add a flag that suppresses warnings and pass outputs, but still allow for errors to be emitted as part of the build process, likely to stderr. (Maybe warning suppression should fall under a different flag, with the --quiet flag implying the warning suppression flag... not sure.)