Félix Saparelli

Right, so it's an FSEvents thing. Unfortunately I can't really mitigate that. However, it will be fixed next release, when upstream watchexec is used here: the backend changes away from...

Okay, so it's not actually an FSEvent thing, because Watchexec was using FSEvent all along too. It might be a Notify 4 vs 5 thing, or it might be something...

This will be properly supported with the new (experimental) filtering engine when it lands later this year: ```console $ env CARGO_WATCH_FILTERER=tagged cargo watch ``` I'll reclose when that arrives

Correction, this will be properly supported via .gitignore and .ignore in the default/normal mode for a future release which will include Watchexec 2.

Well that's... highly annoying. I'll investigate this. In the meantime you can install with cargo-binstall or directly from a build, it will probably help your Dockerfile build times too ^^

Interesting one! I think I can support it, but will report back if I can't. How would you call this pattern (for reference)?

Marking as upstream for inclusion in the project-types crate.

~~I've called it a [meta-workspace for now](https://github.com/watchexec/watchexec/pull/370/files#diff-f1e9660b95f4c4dece5211f30f4117985cc9b90301bcaa3988715380bb63072cR84-R90).~~ Nevermind, "super workspace" is what I'm going with.

Okay, what do you think of this (extract from future help page): ``` -p, --package Watch a package in a Cargo workspace. This is almost equivalent to --watch, but with...

> Could we make them meaningful like ws, crate, ... subcrate? Absolutely! I started with `crate` but it got very repetitive and I opted for foo/bar in the interest of...