-
Notifications
You must be signed in to change notification settings - Fork 21
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
Option clipboard=unnamed ignored on Neovim #55
Comments
Guess I'll have to finally give neovim a go to see what's going on there. I use "clipboard=unnamed" as well. Thanks for the report. |
Great! Thanks |
will it work with |
No, it doesn't. Same behaviour as before. |
Does anyone have an idea about this? I miss easyclip in my setup! |
I work primarily on windows so I can't debug this issue yet. |
Ah, okay. I'd love to fix it but I have a lot to learn about vim plugins
|
Can this issue be related to: neovim/neovim#3141? |
Could be, they might have made the setting backwards incompatible in some
|
I took a brief look at this on a ubuntu virtualbox, and it looks like easyclip is doing things correctly with |
neovim/neovim#3141 has been merged. |
I’ve just updated my neovim installation and it seems to be working now. I thing this issue can be closed. |
I can confirm, awesome! |
I have both Vim and Neovim configured with “set clipboard=unnamed”. It works as expected for both Vim and Neovim: if I yank something on (Neo)Vim, it is placed in the * register; also, if I copy something on another program, again the * register is updated. When I paste something without specifying a register, the content of the * register is used.
Nevertheless, if I enable the Easyclip plugin on Neovim, the “clipboard=unnamed” option starts to be ignored completely. All unnamed operations start to use the " register, not the * one. Vim remains working though.
I'm not sure if this problem should be issued here or on Neovim repository. But the oddity is that it's only happening when Easyclip is enabled on Neovim.
The text was updated successfully, but these errors were encountered: