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
Yank back killed text ctrl+y
stopped working
#72630
Comments
We didn't bind |
@rebornix Currently VSCode is only app on my mac that does not support |
I think this may have broken in Mojave specifically. I recently went from a work computer on Sierra to a personal computer that's running Mojave and noticed this. I'm just guessing at the moment though |
It's not the same as paste ( Although, I suppose that's not a dealbreaker... As a workaround I could map But it seems that vscode is actively overriding the system's |
@rebornix I don't believe this is specific to VSCode, in other Electron apps the behaviour is the same — kill (^k) works, but yank (^y) does not. (e.g.: Obsidian, Slack) |
Spotify is Electron app, but it works (kill & yank) |
I'm not really sure if Electron on the Mac is using a standard Macos text widget that has these bindings implemented or not. However if you go to Code | Preferences | Keyboard Shortcuts and then search for Ctrl-k, it is in fact bound to "Delete All Right". If you remove that, Ctrl-k then does nothing in the editor. So what is likely needed is a solution like @partap proposed, but to be delivered as part of the defaults. I am OK whether it uses the same clipboard (like Emacs does), or a separate one (like MacOS elsewhere does). (In the meantime, I obtained the desired effect manually by installing ctf0's "macros" extension, adding to settings:
and then binding ctrl-k and ctrl-y appropriately.) |
I found an extension which does this and nothing more: wdawson/vscode-bkr. |
@notpeter Yay! 😃 |
Steps to Reproduce:
ctrl+k
to kill text.ctrl+y
to paste the kill text does not work.Does this issue occur when all extensions are disabled?: Yes
Works on all other program except vscode.
The text was updated successfully, but these errors were encountered: