No you cannot run any of those WMs, some of those do have ports with varying degrees of completeness but only sway(i3) and hyprland(hypr) are ready for prime time.
Yes, using waypipe
Yes, primary selection does work along with Ctrl+c although as others have mentioned it forgets when the app you copied from gets closed
Can I use AwesomeWM, XMonad, or StumpWM on Wayland?
Can you run macos software on linux?
Can I run a GUI program over ssh?
This is more of a why would you… Although, waypipe
Does it support the X selection and clipboard protocols?
Too lazy to google, but overall clipboard works as expected, both C-c and text selection. I remember experiencing problems with clipboards in vim (like 2 yrs ago) which were fixed by switching to nvim
Wayland only keeps the clipboard until the application exits. This means a clipboard manager is basically a requirement. Iirc desktop environments might solve those issues by default, but on a standalone compositor just add a clipboard manager and enjoy the history.
I’ve added a keybind for deleting history, but it’d be great to have a way to specify short lived clipboard entries. But this might also be one of those standards that no one implements.
Can I use AwesomeWM, XMonad, or StumpWM on Wayland?
Can I run a GUI program over ssh?
Does it support the X selection and clipboard protocols?
(These are not rhetorical questions, I’m really asking.)
No you cannot run any of those WMs, some of those do have ports with varying degrees of completeness but only sway(i3) and hyprland(hypr) are ready for prime time.
Yes, using waypipe
Yes, primary selection does work along with Ctrl+c although as others have mentioned it forgets when the app you copied from gets closed
Can you run macos software on linux?
This is more of a why would you… Although, waypipe
Too lazy to google, but overall clipboard works as expected, both C-c and text selection. I remember experiencing problems with clipboards in vim (like 2 yrs ago) which were fixed by switching to nvim
Wayland only keeps the clipboard until the application exits. This means a clipboard manager is basically a requirement. Iirc desktop environments might solve those issues by default, but on a standalone compositor just add a clipboard manager and enjoy the history.
Correct, yet I personally don’t find it too useful and sometimes harmful when dealing with, for example, password managers
I’ve added a keybind for deleting history, but it’d be great to have a way to specify short lived clipboard entries. But this might also be one of those standards that no one implements.
deleted by creator