fix: Handle winborder:get return correctly#165
Merged
saecki merged 1 commit intosaecki:mainfrom Jul 16, 2025
Merged
Conversation
Owner
|
Thanks! Can't wait for this to be in stable :) |
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
2 participants
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.
Hey, from what I can tell
vim.opt_global:getalways returns a table, butnvim_open_winexpects either a string for a preset or a table. If a table is passed, it will always get interpreted as a list of border chars, and we'll getinvalid number of border chars.This PR works around that by checking the length of
winborder:getand transforming the value accordingly.