Vitaly Shukela

> ↳ Virtual touchscreen id=16 [slave pointer (2)] It probably means that the virtual touchscreen is ready to go. > `nc localhost 9494 > /dev/virtual_touchscreen` While having this on, if...

> i have 2 screens, so it should be practical no Unlikely. Maybe you want something like multiple mouse cursors - one real and others virtual? Maybe you can set...

Maybe you can supply touch events to qemu some other way, not by emulating the touchscreen on Linux kernel level? Or maybe you can forward evdev to qemu directly, not...

Maybe. Also searching for "parse" on docs.rs should return something relevant. `palette::rgb::FromHexError` should also point to the place where such error may originate - this type is easier to find....

`patelle` crate is in general rather generics-heavy, which makes it complicated, especially for newcomers to Rust. Having more dedicated functions like `to_hsv()`, `to_rgb()`, `to_rgba_u32()` that does the same as already...

I haven't used dnscache for myself for a long time. If you need just minttl then maybe a simpler DNS proxy (without cache) can be implemented that just patches TTL...

Shall there be a policy about valid keywords in Cargo.toml? Maybe `cargo publish` should reject invalid (unsearchable) keywords? What keyword should be used in relation to [std::any::Any](https://doc.rust-lang.org/std/any/trait.Any.html)? Literally `std::any::Any`? Also ...

Anyway, if there are no search results due to search query being too short (or something), some special message should be shown, like "Too many results to display. Please narrow ...

As a workaround, the list of words may be just copied from PG. Pseudocode: ```rust let number_of_search_results : usize; let search_query : Set; let list_of_known_stopwords: Set; let message = if ...

Looks like I was using incorrect base address. Retrying with 0xc0008000 produced usable Module.symvers file. Maybe the tool should detect attempts to use it with incorrect base address and show...