bacon reacts to every inotify event, possibly seeing a broken project about bacon HOT 8 OPEN

It looks like your vim has a weird save strategy. It's not supposed to remove files when writing them. Any idea why it does that ? Any special setting ?

from bacon.

I removed my vim config before reporting this. If you can't reproduce this, I can investigate further to see if there's something about my system elsewhere that's driving this, but I doubt it.

from bacon.

If you can't reproduce this

No, I never observed this, and probably not many people did, because it would have been reported otherwise, as it seems to break compilation.

from bacon.

I'm not sure if this is 100% related, but bacon often does rerun in the middle of editing a line, leading to compilation errors in my editor as well (RustRover). Often it doesn't seem to pick up the finish of the line, so I need to, add a space or similar to force it to rerun.

from bacon.

I'm not sure if this is 100% related, but bacon often does rerun in the middle of editing a line, leading to compilation errors in my editor as well (RustRover)

You mean your editor automatically saves your Rust files when you're in the middle of a line ? You should configure it differently.

from bacon.

Yes the Jetbrains family of editors saves continuously. After some googling and twiddling around, this is not something that can be disabled, even after tweaking all there is to tweak that I can find. My issue isn't necessarily that bacon runs continuously on each save ( that seems sensible enough, I imagine it can't tell them apart )

However, the problem for me is that bacon gets "stuck" if it compiles something with an error, and the error has been fixed before the compilation is done. E.g. see the following loom to demonstrate the problem (at around 15 seconds in)

I've tried to replicate the same problem with cargo-watch which seems to handle this case successfully (it also has a debounce parameter which removes most of the churn from repeated savings. See this loom as an example.

Totally open to the fact that this might be a separate issue than the original one - although I felt like they're reasonably similar in that it seems to be related to bacon running too early in the process, and not properly rerunning.

from bacon.

not properly rerunning

This looks like a bug and isn't expected

from bacon.

That's fair - I've split it into a different issue

from bacon.