Disable winbar on neovim 0.8.0 and later #387
Open
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
|
Also a separate issue I found, that seemed unrelated to this issue or this fix, is the popup can appear broken in certain scenarios when you have the same buffer in 2 splits, see this screenshot:
|
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.
I found a pretty obnoxious bug that can occur when a winbar is setup with the matchup floating windows where it can trigger
E36: Not enough roomerror.I've attached a video of the error occuring, and while I did try to solve it on the lualine side by conditionally disabling winbar in floating windows, I couldn't ever seem to get it to work. The only fix I found was just to wholesale disable winbar in these floating windows:
CleanShot.2025-04-26.at.13.48.01.mp4
Unclear if this is the preferred way to do it, but I imagine a winbar shouldn't ever be shown in these scenarios regardless, so felt safe? Happy to change it to check for an option though if you'd prefer.