Lennart Kolmodin
Lennart Kolmodin
And yes, the work should ideally not be done on the UI thread to start with. It could be done in a service worker, but that's future work :)
Oh, sure, I'll update the instructions. I've got a lot going on now, but I'll get to it shorly I hope.
No, sorry. Can someone take over, if this PR is still relevant?
The application can solve it in whatever way it wishes if we provide the building blocks.
It wouldn't be efficient to only read a single event. For performance reasons they should be read in batch. It's also essential to wait until there is enough events to...
Looks like you're describing `readEvents` in the top post.
At least on Linux it'd block until something is available, and then return that. It won't be a lot, which is why there should be a threshold before reading.
Hi, can you share a snippet of your use case? If you intend the daemon process to stop when inotify is done, maybe you can use `withINotify`? ```haskell daemon =...
The log shows some weird issues. Take `test001` for example. It registers for `Open` and `Close` events. It then says that it expected the following event entries; ``` > Accessed...
I haven't used `deriving via`. So there's not a common pattern for how to name the additional newtype? Did I get it right that the first "simple usage" can just...