I start my coding workspaces in tmux sessions which persist when I log out. If I switch from a wayland session to an x11 session, then my copy and paste functionality in those neovim sessions are broken because it’s still trying to use wl-copy. To be more precise:
- Start a wayland session.
- Open a terminal and start a tmux session.
- Open neovim and do some work.
- Log out of wayland, log into an X11 environment
- Open a terminal and reconnect to the tmux session
"+ybroken.clipboard: error invoking wl-copy: Failed to connect to a Wayland server...
Restarting neovim isn’t sufficient. I have to restart the entire tmux session or switch back to wayland. Is there some short cut I can take here?
Heho,
Just a guess. The tmux session may persist env. Thus nvim reads eg DISPLAY and thinks it must still be a wayland compositor.
Hope it helps
This is exactly what happens. Actually the whole Wayland/xorg thing is not necessary, simply exiting a Wayland session and starting a new one will probably have the same effect, might depend on compositor. But it doesn’t help knowing that it’s the cause, I’ve known it for years, no closer to a solution. Obviously closing the tmux session and starting over is a “fix” in the same way that turning the machine off and on again is a fix. Kinda defeats the purpose of persistent tmux sessions.
Thats for sure what’s happening. The remaining error message makes that clear but I couldn’t copy the full message