-
Notifications
You must be signed in to change notification settings - Fork 120
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
Issues when OSC 52 is in use #636
Comments
Issue seems to be with this function:
I can reproduce with OSC 52 on:
Now, highlight a line and yank it, then enter |
Did you mean |
I can probably debug, but I would like more info about what "On insert, if you've ever been in a visual mode since Vim started, yank the contents of the last used register, and trim it, etc..." Is that correct, and if so whats the main use of this? |
It's used by the snippets engine very rarely, for |
"Currently selected text" could also mean just the "currently highlighted text" in visual mode, no? Do we necessarily need to get a register? The text in a register could have been selected weeks ago. |
Make sure you have done the following
blink.cmp
Bug Description
Remote development is more popular than ever.
Often times the simplest way to get copy and paste working on a remote machine it ouse OSC 52 term codes.
Blink.cmp seems to be doing something behind the scenes which causes unnecessary OSC 52 termcodes. This could be spurious copy or pastes to the system buffer.
I'm noticing when I install Blink.cmp, as soon as I copy something into the system register, changing VIM to
INSERT
mode causes OSC 52 to wait for a response from the terminal.As soon as I remove Blink.cmp this is no longer an issue.
Relevant configuration
No response
neovim version
v0.11.0-dev+1369-gb03e790cd (nightly)
blink.cmp
version: branch, tag, or commitv0.7.4
The text was updated successfully, but these errors were encountered: