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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug Report] vim.useSystemClipboard: false
affects default Vim behaviour.
#2051
Comments
Submitted bug report to VSCodeVim/Vim#2051
@Vvkmnn It's likely that the library we're using for interfacing with the system clipboard is crashing when you try to do yy. |
Fair enough. I'll try and use other registers for now. Would you recommend building from source or trying the Insider version? Not sure that'd fix it; just thinking out loud. I could also try logging the event if that helps trace it. |
@xconverge I seem to remember some other person had this problem. Do you remember how he fixed it? |
"vim.useSystemClipboard": false
affects default Vim behavior.vim.useSystemClipboard: false
affects default Vim behaviour.
Tore away at my config until I got it working; turns out it wasn't this plugin's fault at all. Sorry guys. The true issue appeared to be launching FIX: Just launch Vscode outside Tmux (or help figure out the error: microsoft/vscode#24112) Keep up the good work. 鉁岋笍 |
The VSCodeVim team prioritizes issues based on reaction count.
BUG REPORT
The
"vim.useSystemClipboard": false
parameter screws up VscodeVim's behaviour. Not entirely sure why, but I'm happy to provide additional context as necessary.Opened
code
from Terminal, and iTerm2 just to check; found the same error.Environment:
What happened:
Here' a gif summarizing the workflow. tl;dr: Flipping this parameter to
true
makesyy
,dd
, etc. not work.What did you expect to happen:
I expected text to be copied to the System Clipboard, and for the default Vim behaviour to work. Neither does.
How to reproduce it:
This is a vanilla install on a new machine. Already restarted a few times.
Open to suggestions.
Related Issues
#1830
The text was updated successfully, but these errors were encountered: