Manipulating vim.g.clipboard
is the trick. I'll have to write some command that sets the clipboard provider directly.
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
this post was submitted on 12 Sep 2024
20 points (100.0% liked)
Neovim
2155 readers
1 users here now
founded 1 year ago
MODERATORS