Although this patch might seem a bit like a hack, it works surprisingly well in Safari.

Thank you for the patch! Could this fix be sent upstream tohttps://github.com/microsoft/vscode? At a glance it seems like something that should be fixed upstream to me.

The VS Code folks can probably give a better review than I can, but my gut says that specifically reacting to Vim keybindings in the core might not be the right implementation.

@code-asher As you mentioned, I don’t think VSCode would accept this patch. Given that WebKit (the core of Safari) has no plans to open the clipboard API, and considering the limitations of both VSCode's architecture and WebKit, supporting this in a VSCode extension isn't feasible. For now, the only viable solution is to modify the VSCode core via a patch.

Even if this PR doesn’t get merged, that’s perfectly fine—I totally understand. While this patch works, it is indeed quite a hack. My intention is simply to provide this solution for anyone who might find it useful.

That makes sense! Yeah I think it is not something we should merge so I will close but we can use this as an example if anyone else has issues.

Speaking of, what is the issue exactly? Is it that sometimes pasting does not work, specifically when pasting in rapid succession?

Speaking of, what is the issue exactly? Is it that sometimes pasting does not work, specifically when pasting in rapid succession?

When you install VIM extension and enable "vim.useSystemClipboard": true,p (paste function) in vim mode will be unavailable (in safari), because vscode's clipboard API callsnavigator.clipboard.readText(), which must be called in events directly triggered by the user in webkit-based browsers, and vscode calls this API in the request of VIM Extension.