Thanks @Narsil,

Following your suggestion, I cleaned up the documentation and split the "OS Caveats" section into a separate section for each of the listen and grab functions, making them more prominent and explicit

I've run the cargo tests and clippy checks you suggested on windows and MacOS, and all the tests pass.

Could you please review?

In order to pass quality, you should change the lib.rs file first, then run cargo readme > README.md.

you mean do them as two separate commits?

also, on windows 10, cargo readme > README.md converts README.md to a UTF-16 encoded file, which git interprets as a binary file. i had to do cargo readme -o README.md instead.

If i get a chance, i'll open up another PR with some basic contributor guidelines, based on what I've learned so far :)

not sure how I managed to lose that semicolon, but it's been re-added, and cargo test, cargo clippy, and cargo fmt have all been successfully run

oh that's an interesting error...

i see in the github ctions workflow file that only the serialize feature is enabled, and there's a note saying that grab is not supported in linux. is this a holdover from before the evdev refactoring, or is grab testing on linux disabled for some other reason?

I just booted up my linux laptop, cloned the repo to it, and ran the doctests with all features enabled, and it passed all tests.

should i add a //! #[cfg(feature = "unstable_grab")] line to each section of the grab example, or should i modify the rust.yaml file to enable unstable_grab in linux?

Protect the example with #[cfg] grab is still not a by default feature :)