hide mapping boilerplate #6
Merged
Conversation
This file contains 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.
The default view is a bit compact, and even after configurating it a bit wider, many longer strings are shortened to an illisible "...", which kind of defeats the purpose of which-keys...
(consider one of my own mapping :
nnoremap <silent> <leader>a <cmd>lua require('lspsaga.codeaction').code_action()<CR>, not saying it's best pratice but many users' may look like this)This should help a little bit, by removing the standard boilerplate cluttering the mappings.
Probably not an exhaustive list, but this should be 'safe', ie not remove any substring that is an important part to understanding what the mapping do