fix: Read keymaps from user modified config table#1
Merged
StackInTheWild merged 1 commit intoStackInTheWild:mainfrom Sep 18, 2025
Merged
fix: Read keymaps from user modified config table#1StackInTheWild merged 1 commit intoStackInTheWild:mainfrom
StackInTheWild merged 1 commit intoStackInTheWild:mainfrom
Conversation
StackInTheWild
approved these changes
Sep 18, 2025
Owner
StackInTheWild
left a comment
There was a problem hiding this comment.
Yeah right, thanks for the Pull Request I didn't noticed
Contributor
Author
|
Yep. By the way, congrats on your kid! I too will soon be a sleep deprived father, I believe 😬 |
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
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.
Small typo, I think. This PR changes the
vim.keymaps.setto read from the user modified config object instead of default, which allows user specified mappings to take precedence over defaults.