Skip to content
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

yyp paste garbled text when the line contains only Chinese characters and 'vim.useSystemClipboard' is on #1125

Closed
localvar opened this issue Dec 6, 2016 · 1 comment · Fixed by #1559

Comments

@localvar
Copy link

localvar commented Dec 6, 2016

Please thumbs-up 👍 this issue if it personally affects you! You can do this by clicking on the emoji-face on the top right of this post. Issues with more thumbs-up will be prioritized.


What did you do?

  1. edit vscode config to enable 'vim.useSystemClipboard' and restart vscode
  2. create a new file with below content
通过将设置放入设置文件中来覆盖设
  1. open the file and yyp on the line

What did you expect to happen?

the file content becomes

通过将设置放入设置文件中来覆盖设
通过将设置放入设置文件中来覆盖设

What happened instead?

the file content becomes

通过将设置放入设置文件中来覆盖设
�惽?\緥n�>eeQ緥n�噀鯪-Neg唹講緥

Technical details:

  • VSCode Version: 1.7.2
  • VsCodeVim Version: 0.4.9
  • OS: windows 10 professional build 1607
@localvar localvar changed the title yyp paste mess when the line contains only Chinese characters and '"vim.useSystemClipboard' is on yyp paste garbled when the line contains only Chinese characters and 'vim.useSystemClipboard' is on Dec 6, 2016
@localvar localvar changed the title yyp paste garbled when the line contains only Chinese characters and 'vim.useSystemClipboard' is on yyp paste garbled text when the line contains only Chinese characters and 'vim.useSystemClipboard' is on Dec 6, 2016
@xconverge
Copy link
Member

This is fixed for macOS and linux but not windows yet unfortunately! Related sindresorhus/clipboardy#11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants