-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Integration with comments broke with recent versions #9270
Comments
This should definitely be fixed. Comments can already be closed via shift+escape so escape by itself should be reserved for changing modes. Right now I'm working around this by using ctrl+[ to change modes. |
This appears to be an addition to either vscode itself or the Github Pull Requests extension, as Escape closes the comment widget with VSCodeVim disabled. Disabling VSCodeVim, enabling "Developer: Toggle Keyboard Shortcuts Troubleshooting" and then looking at the vscode "Window" output suggests that this is not triggered by a regular keyboard binding since no command is invoked:
|
Found the underlying issue in vscode and created a ticket: microsoft/vscode#231674 |
Describe the bug
A few releases ago, it became possible to use VSCode Vim when editing comments from the Github Pull Requests extension.
This was absolutely amazing, and game changer when writing comments. (Vim ❤️)
However since a very recent release (of VSCode probably), pressing escape while in insertion mode, instead of returning to normal mode, cancels writing the comment, closes the dialog and discards the text.
In one hour of reviewing PRs, it's the 4th super detailed comment I have to entirely rewrite because it's hardwired in my brain that I can press escape to exit insertion mode, and that actually closes the comment dialog. (So by the way there's no way to exit insertion mode.)
I'm going crazy. 😭
Please help! 🏝️🏳️
Thanks in advance!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Exits insertion mode, not closing the dialog.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: