configuration file : user feedback needed about bacon HOT 7 CLOSED

I'd like to set a base command other than cargo (x.py, for the rust compiler).

from bacon.

Also, x.py doesn't support --color always, but maybe I should just fix that upstream.

from bacon.

Right now the idea is to have a bacon.toml file in the project's dir but I'd like to have opinions about that.

Another option is to make the configuration part of Cargo.toml directly, the way docs.rs does it: https://docs.rs/about/metadata. But I don't have strong opinions on whether that's better or worse than bacon.toml.

from bacon.

I'd also like to set summary mode on by default. Right now it's opt-in with s, but I rarely want to see the whole error the first time I start up bacon.

from bacon.

The bacon.toml file is expected to look like this:

default_job = "check"

[jobs]

[jobs.check]
command = "cargo check --color always"

[jobs.check_windows]
command = "cargo check --target x86_64-pc-windows-gnu --color always"

[jobs.clippy]
command = "cargo clippy --color always"

[jobs.tests]
key = "t"
command = "cargo test --color always"

It stays optional and is generated with a default content (check+clippy) when running bacon --init.

To start a given job, you may do bacon --job clippy.

from bacon.

I've still not decided for

command = "cargo check --target x86_64-pc-windows-gnu --color always"

or

command = ["cargo", "check", "--target", "x86_64-pc-windows-gnu", "--color", "always"]

The latter is more powerful but so painful to type in common cases...

from bacon.

I'd prefer the second version, I don't expect many people to use the configuration file so it's ok to make it a little harder to write.

from bacon.