Bacon gets confused when the build command has unexpected output

[jyn514]

This is a screenshot of bacon after saving a modified file, after bacon starts up for the first time.

I would expect the extra output to be either hidden or shown with proper line wrapping, not with weird indentation.

You can reproduce by running bacon on rustc (rustc strikes again!) with the following bacon.toml:

default_job = "check"

[jobs]

[jobs.check]
command = ["x", "check", "--color", "always"]

[jobs.clippy]
command = ["x", "clippy", "--color", "always"]

[Canop]

Can you try with

[jobs.check]
command = ["x", "check", "--color", "always"]
need_stdout = true

I have two questions:

• on what OS do you run this ?
• did you change x.py to accept the color argument ? Or what's the trick ?

[jyn514]

need_stdout = true did not help. I ran this on x86_64-unknown-linux-gnu (Debian 10), although I wouldn't expect that to affect anything.

did you change x.py to accept the color argument ? Or what's the trick ?

Yes, that was rust-lang/rust#79004; you may need to update your fork of the repository.

[Canop]

I don't reproduce and I don't understand how x's output can travel up to the screen.

Can you reproduce with the last commit (which pipes the command output to null) ?

[jyn514]

Works fine on latest master, thanks for the quick fix :)