Add g:which_key_floating_opts_explicit and g:which_key_floating_vars #228
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
rene-descartes2021
force-pushed
the
window-opts
branch
from
4af795b
to
8ea8b80
Compare
rene-descartes2021
force-pushed
the
window-opts
branch
from
8ea8b80
to
e863411
Compare
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.
Fixes #210 and helps somewhat with #180.
Doesn't add any complex abstraction over the different Vim/Neovim APIs. Just passes on the options the end-user wants and let Vim deal with any problems.
g:which_key_floating_opts_explicitentries are set on the floating window at creation via the{options}parameter, e.g.border.g:which_key_floating_varsentries are set on the floating window after creation viasetwinvar(), e.g.&winblend.The documentation details both examples.