this post was submitted on 12 Sep 2024
20 points (100.0% liked)

Neovim

2159 readers
3 users here now

founded 1 year ago
MODERATORS
erlingur@programming.dev
howarddo@programming.dev
kahnclusions@programming.dev
lung@lemmy.world
20
How do I change the clipboard program that neovim uses? (programming.dev)
submitted 1 month ago by sudo@programming.dev to c/neovim@programming.dev
4 comments fedilink hide all child comments
 

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:

  1. Start a wayland session.
  2. Open a terminal and start a tmux session.
  3. Open neovim and do some work.
  4. Log out of wayland, log into an X11 environment
  5. Open a terminal and reconnect to the tmux session
  6. "+y broken. 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?

all 5 comments
sorted by: hot top controversial new old
[–] sudo@programming.dev 4 points 1 month ago

Manipulating vim.g.clipboard is the trick. I'll have to write some command that sets the clipboard provider directly.

[–] gudu@programming.dev 3 points 1 month ago (2 children)

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

[–] bjornsno@lemm.ee 4 points 1 month ago

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.

[–] sudo@programming.dev 2 points 1 month ago

Thats for sure what's happening. The remaining error message makes that clear but I couldn't copy the full message