Famiu Haque
Famiu Haque
> Mot sure we want window layout to change on expression evaluation, but we could provide a **static** value to disable winbar locally like `%{%}` or whatever would make sense...
> Option to disable an option sounds like an anti-pattern. Id rather just identify a good sentinel value. Fair criticism. But not sure what would be a good sentinel value,...
> Except that 'winbar' already controls whether it is displayed or not, so i think we should rather make that control complete rather than adding a new option only for...
> @famiu I think having the ability to disable the winbar per windows makes sense if you are using sidebars like a symbol viewer or file tree sidebar. I also...
> I also get this error when using `tabe file.txt` could you be a bit more elaborate and give steps to reproduce with `nvim --clean`? Being able to reproduce this...
> ```lua > vim.api.nvim_set_option_value("winbar", "hello world", { scope = "local" }) > ``` I discovered that there's an easier way to reproduce the issue: 1. `nvim --clean` 2. `setlocal winbar=foo`...
There isn't enough room on the floating window since it's only a single row and the only row cannot be a winbar, and winbar will not resize float windows by...
It seems like this is still intended behavior since floating windows are supposed to act like split windows but just floating, so it's desired for them to inherit all options...
> I know the PR is still draft, but is there a reason this is done for lua only as opposed to the API? It takes a Lua callback
> > Closes #19103 > > That issue doesn't give a use case. Is the complexity worth it? It doesn't add that much complexity imo, if anything it adds structure...