You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ or
39
39
40
40
bacon ../broot
41
41
42
-
### check all targets (tests, examples, etc)
42
+
### check all targets (tests, examples, benches, etc)
43
43
44
44
bacon --job check-all
45
45
@@ -129,6 +129,16 @@ Similarly you don't have to stop bacon when you want to use cargo to build the a
129
129
130
130
Bacon is efficient and doesn't work when there's no notification.
131
131
132
+
### Can I have all code always checked, including tests, benches and examples ?
133
+
134
+
You can set the dedicated `check-all` job as as default in the bacon.toml file:
135
+
136
+
```TOML
137
+
default_job = "check-all"
138
+
```
139
+
140
+
Similarly, if your test units are fast enough, you may run them as default, either by editing the default job, by pointing to a new default job, or by creating a new one.
141
+
132
142
### What are the supported platforms ?
133
143
134
144
It works on all decent terminals on Linux, Max OSX and Windows.
@@ -151,7 +161,7 @@ A solution is to add this to your init.vim file:
151
161
152
162
set nowritebackup
153
163
154
-
This doesn't prevent vim from keeping copies during editions, it just changes the behavior of the write operation.
164
+
This doesn't prevent vim from keeping copies during editions, it just changes the behavior of the write operation and has no practical downside.
0 commit comments