feat(main): adds configuration option to set the spelling plugin's trigger #910
+13
−11
Conversation
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
Added a "trigger" configuration option under "spelling". With it, the user can assign the key combination to trigger the spelling plugin. The default value is set to be the previously hardcoded value "z="
de-abreu
changed the title
de-abreu
changed the title
de-abreu
changed the title
|
This PR is stale because it has been open 30 days with no activity. |
github-actions
bot
added
the
stale
iSplasher
added a commit
to isplasher-forks/which-key.nvim
that referenced
this pull request
Jun 20, 2025
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.
Added a "trigger" configuration option under "spelling". With it, the user can assign the key combination to trigger the spelling plugin. The default value is set to be the previously hardcoded value "z=".
Description
The usage of Whichkey is imperative when extensively modifying default keybindings, as it allows one to document all changes made while they are being made at the level of configuration. In turn, having hardcoded keybindings inside WhichKey is counter productive to that goal.
Related Issue(s)
Solves #866