3 ms·
> Now why does wayland break xclip and vnc? Does it matter why? If I use VNC to do my work, it is absolutely impossible for me to switch to wayland, no matter
by perryizgr8 6y ago
> Now why does wayland break xclip and vnc?
Does it matter why? If I use VNC to do my work, it is absolutely impossible for me to switch to wayland, no matter how justified the reasons are.
- kuschku 6y agoIt does, because it explains why this change has to be done by VNC client/server devs, and can’t be done in the wayland protocol or compositor. If a new replacement would have the exact same set of supported use cases as the original, it wouldn’t be useful. The point of wayland is that it enables some new use cases, while restricting some older ones. Wayland is still powerful enough to implement VNC (weston supports RDP in both directions) or xclip (KDE’s klipper works just fine under wayland). It just requires effort from third parties.
- ddevault 6y agoNo, it doesn't. What matters is that xclip and vnc aren't broken on Wayland. I mean, xclip is, but it's called xclip for a reason. The use-case is not broken, and is fulfilled instead by a tool called wl-clipboard.