Proc

Ok thanks, problem is that this will make it kinda guesswork to trace down (and requires more work to inspect). To rule out the possibility of user limitations regarding file...

I'm raising the inotify limit issue as something to be fixed via better error reporting. Possibly looking into whether `inotifywatch` has more than simple error-code catching to detect this issue....

Note that a similar issue is fixed in v5: https://github.com/notify-rs/notify/issues/266 Although the error message is different. Needs confirmation.

I sadly can't test this at all, as I don't own an m1 device. And this can't be simulated by gh-actions? Is there a specific conditional compilation [architecture](https://doc.rust-lang.org/reference/conditional-compilation.html?search=#target_arch) we could...

So the question is: Do we want to add this error-code workaround into notify ? The default-watcher is just an alias, so if you'd create an inotify watcher manually, you'd...

> document the behaviour Definitely. I was thinking about a way to make the default-init able to catch such a case without inducing a ton of overhead. Currently the default...

I'm adding a note about this in #395 A correct fix is a little bit more tricky.

It was removed due to problems, so we would have to re-implement it for a real 5.0 release.

> @0xpr03 maybe using https://crates.io/crates/rjdebounce ? I don't think we want to add more dependencies just for debouncing. Also looking at the code this does not do what we want....

> I need to have an option to do things without using thread channels What exactly do you mean without threads ? Notify certainly doesn't support no-std and even without...