Closed DanielFGray closed 1 year ago
I consciously made it behave like this so that the winbar won't toggle itself too much when navigating around. Do you have a use case for the feature you're suggesting?
In some filetypes where there's no information from treesitter (eg sql) it just feels like wasted space.
I only just realized that the bar isnt "floating" but is instead pushing the viewport down a line..
I wonder if it would be possible to have an option to be shown in a floating window that that stays docked to the top, and could easily be toggled when empty without shifting the buffer around?
I wonder if it would be possible to have an option to be shown in a floating window that that stays docked to the top, and could easily be toggled when empty without shifting the buffer around?
Neovim handles winbar highlights (where barbecue is) significantly different from buffer highlights (like a floating window), which is a huge obstacle to this solution because it'd need the whole project refactored to get it working.
for whatever it's worth, I've switched to using navic directly in lualine, but I am missing the clickable feature of barbecue
I've made barbecue go hidden when the language server doesn't provide any information (no textDocument/documentSymbol
capability) and the dirname
and basename
parts are disabled.
Try bugfix/exclusion
branch and see if this was what you wanted. Then I'll merge.
I like this, it does help. I do wish it went a bit further, and also hid when eg on a blank line and theres nothing shown, but considering the limitations it seems this is as good as we can get. Thanks!
Requirements
Problem
sometimes when navigating, navic returns an empty string, and then theres an empty winbar covering up text
Solution Suggestion
when navic returns an empty string, the winbar should toggle its visibility
Workaround
No response