Fix TAB key in edamagit - #395
Open
stevenguh wants to merge 1 commit into
Open
stevenguh wants to merge 1 commit into
stevenguh wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
This commit addresses the broken TAB key functionality within edamagit, which was caused by a change in VSCodeVim's default keybindings to support Next Edit Suggestions. VSCodeVim/Vim@bba5de0 Similar documentation update was made on edamagit as well kahole/edamagit@c7a5221. User will need to perform vscode keybindings reconfiguration to fix this.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #391
This commit addresses the broken TAB key functionality within edamagit, which was caused by a change in VSCodeVim's default keybindings to support Next Edit Suggestions. VSCodeVim/Vim@bba5de0
Similar documentation update was made on edamagit as well kahole/edamagit@c7a5221.
User will need to perform vscode keybindings reconfiguration to fix this.