-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clipboard history #1470
Comments
The implementation would be a little tricky since we pass file descriptors between the windows and not the actual contents themselves. |
This should be possible, but it's not going to be done for some time. |
Sure, no problem! Thank'you for your interest. |
Wouldn't it be more sane to make a protocol for clipboard access with events on update? It can be useful not only for clipboard managers but also for dictioonaries and other stuff. |
If I understand correctly, clipboard managers in wayland can't work anymore, by design. According to this comment it's the compositor's responsibility to implement clipboard managing, because apps are not privileged enough.
Basically it should be as simple as storing clipboard events incrementally in a file, instead than replacing the previous selection; for security and compatibility with existing set-ups, the default history length would be 1. Then it's up to third party apps to retrieve and display the clipboard's history (for example from sway-msg).
The text was updated successfully, but these errors were encountered: