Comments (13)
I think bacon 2 makes this issue obsolete.
I'll keep the issue open til the release of bacon 2, though, and then it can still be discussed.
What feature in v2 made this issue obsolete? My usecase is to be able to watch both tests and clippy output at the same time. Right now, it seems to require needing to hit c
and t
to toggle between which one is running, or requires running two instances of bacon
in seperate terminals. Am i missing something here?
from bacon.
Ditto, running test
and clippy
in the same term would be a space saver.
from bacon.
I would like this as well, it would be nice to be able to just run bacon
and have it run all jobs at once.
from bacon.
You mean in sequence ? One after the other one and stopping at the first one with things to say ? Can you give an example of the involved jobs ?
from bacon.
I meant more running them in parallel, like in separate tabs. But now I realize that just opening separate terminal tabs and running multiple bacon
s is probably the best way to do that.
from bacon.
I often have 2 parallel bacon terminals, when I want some code to be checked with separate targets or features, mostly for cross compilation, but I never need more.
When you run bacon test
, it effectively does the bacon check
too: the tests will be ran if there's no error.
That's why I ask about your use case, to understand why you'd need "all jobs".
from bacon.
I have separate ones for cargo test
and cargo clippy
, since I think cargo test
doesn't run clippy lints. Separate terminals seems to work fine for me though.
from bacon.
I could define a way to chain jobs, like bacon test+clippy
where clippy is ran if there's no failing test.
from bacon.
That's actually similar to my usual workflow where I'd use cargo watch
to run clippy
then test
, which worked well because if clippy
failed with a compiler error then there's no need to try to run test
. So far, I'm liking bacon
's output for clippy
much better, so I'm using it for that, but I still want the full output for test
so I'm still running that under cargo watch
.
from bacon.
If something relevant is missing from bacon test
, another issue might help.
from bacon.
Another, maybe simpler idea: how about adding a job for cargo checkmate ? This would run all "interesting" jobs in one pass.
from bacon.
I think bacon 2 makes this issue obsolete.
I'll keep the issue open til the release of bacon 2, though, and then it can still be discussed.
from bacon.
I'm just discovering Bacon — so far, it's really brilliant. I had been building my own things with watchexec
& Taskfile
when this does exactly what I want and is really fast.
Allowing multiple jobs is a feature that would be great — for example I'd like to see clippy lints, but also run tests.
Having them either consecutive or in parallel would be broadly equivalent, since cargo
locks the build cache, which takes most of the time.
Until then, I'm just running multiple runs of Bacon — it's fine, though means folks have to learn which things to run; ideally we could give a standard bacon
from our project, and it would launch the jobs we recommend running.
from bacon.
Related Issues (20)
- Screen doesn't clear when the file watcher restarts a long-running job HOT 8
- run tests with `-- --nocapture` option HOT 4
- bacon reacts to every inotify event, possibly seeing a broken project HOT 8
- Run multiple jobs after each other HOT 5
- Difference between how cargo clippy and bacon clippy treat tests HOT 2
- Fails to build with nightly 98aa3624b 2024-02-08 in ahash-0.8.2 HOT 4
- Bacon fails to properly rerun on changes that happen while compilation is ongoing HOT 7
- `bacon test` doesn't recognize `--features` HOT 4
- Can't seem to make `bacon test --no-default-features` work HOT 2
- Can't build on M3 MacPro with sold linker HOT 5
- wheel scrolling doesn't work in tmux / linux HOT 6
- Not displaying correctly on Windows Terminal, offset by one line HOT 5
- `on_success` doesn’t trigger when there are warnings and `allow_warnings = true` HOT 1
- [feature request] Expand env vars in job command HOT 3
- Inconsistent stdout flushing when using `bacon run`
- Tests are only run on workspace default package
- 2.18.0 build with --locked fails on nightly HOT 3
- Show the error line number in doc test summaries instead of the block line number. HOT 1
- Inconsistent terminal behaviour on windows HOT 8
- Show color in doc test results HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bacon.