Tommaso Laurenzi

an empty winbar could be shown by returning `" "` instead of `""` ? or perhaps distinguishing between an empty string and `v:null` or `v:false`

that's absolutely right, I did not think it well

Setting local winbar for every buffer except a few ones seems sub optimal. The reason for this is that if local winbar is unset, it will fall back to global...

inspired from @shaunsingh added custom mappings as an aside, I would reconmend improving the shortcut highlight group, single keys (eg.: 'q') or symbols (eg.: ' q') are not highlighted. it...

I think you should create a `short_line_left` version of `ViMode`, like ``` ('galaxyline').section.short_line_left[1] = { SViMode = { ... } ``` This way it will be a different object and...

Unfortunately this is not a solution, as it voids the feature of not displaying the winbar on specific buffers. If the devs are not willing to endorse the hackish mechanism...

@joehannes this is hardly a heirline issue. And there's no workaround at the moment except using `global` winbar. Try for yourself: ``` nvim --clean :setlocal winbar=foo # write a few...

temporary fix: ```lua require("heirline").setup(StatusLines)--, WinBar) require("heirline").winbar = require("heirline.statusline"):new(WinBar) vim.opt.winbar = "%{%v:lua.require'heirline'.eval_winbar()%}" ``` this will setup global statusline instead of a local one until this is fixed

I am sorry but I need more context to help you. How do you specify the fg/bg colors of the statusline? Please see the latest updates to the cookbook for...

`stop_at_first` has been superseded by the more versatile `pick_child`. To get the same behavior change ```lua ... stop_at_first = true ... ``` to ```lua ... init = require'heirline.utils'.pick_child_on_condition ... ```...