Alex Bennée

So we need to know: [ ] - how android signals it's taking the pointer device (does it even need to)? [ ] - how to capture the pointer and...

I've going to guess for the wayland side it's this unstable API: https://wayland.app/protocols/pointer-constraints-unstable-v1

@yxles-dev I think so - at least I think the mapping from mouse to touch is done by Android itself rather than the app taking direct control of an external...

I've tracked down the pointer capture in inputflinger: ``` void CursorInputMapper::configure(nsecs_t when, const InputReaderConfiguration* config, uint32_t changes) { ``` where there is logic to deal with changing the setting: ```...

So as I understand the Android input stack the InputReader is responsible for feeding the data from the underlying system so it stands to reason when the .mode is updated...

The commit 78f97b3263053c388080a738b56499139517c3b6 added support to the Input Reader for pointer capture. Maybe I can see where the underlying config happens there.

I haven't personally tested it but if you look at the buffer it should show why it failed. Is rsync installed and visible in Emacs' path?

If you take that command and run it locally on your windows shell does it work? Have you got an SSH agent setup for passwordless syncing?

I expect it is a a CR (without a newline). However we do extract the completion percentage in `dired-rsync--filter` and expose it via dired-rsync-modeline-status for the modeline. You could do...

So is this a bug in the underlying process spawning code?