Wayland support

[rektide]

Wayland is a new display manager that's about to ship as a default option in the upcoming Red Hat 8, and will be seeing increasing adoption on additional distros as well.

Best resource I've found with resources for talking to the Wayland clipboard is this stackoverflow.

(Alas at the current time Wayland is a pretentious gasbag that declares only input events are supposed to be able to write to the clipboard, but it appears to be up to the compositor/desktop-env to enforce this. Grah.)

[bazzargh]

Was wondering about how to do this in wayland too, found this https://github.com/bugaevc/wl-clipboard ... seems very new so ymmv

[ralsei]

So, stressing the fact that I'm NOT a JS dev by any means, I tried my hands at this: the results can be found in the wayland branch of my fork https://github.com/ralsei/clipboardy/tree/wayland. This probably broke X support as well due to a couple of hacks I did.

The aforementioned wl-clipboard is now relatively mature and ready for usage. The problem is that wl-copy, the Wayland equivalent to xsel etc, forks to the background.

Something would have to be done to allow wl-copy to fork. Don't know how to pull that off. Would be the equivalent of echo input | wl-copy -f & in shell.

[jcorbin]

Something would have to be done to allow wl-copy to fork. Don't know how to pull that off. Would be the equivalent of echo input | wl-copy -f & in shell.

So why does it matter to this library that wl-copy forks? What needs to be done about that?

Asking as a wayland user quite keen to use this package, and willing to put in the time implementing $whatever you'd imagined here...