Closed romgrk closed 1 year ago
Is the
config.options.hide
option really that useful? E.g. I see this line:if hide.alternate or hide.current or hide.inactive or hide.visible then
but I don't understand why users would hide those buffers.
See #298. The primary purpose is hide = {inactive = true}
, but hide = {current = true}
can also be useful (since with set laststatus=3
, you can have one global statusline that shows full information about the current buffer). hide = {visible = true}
can be useful with laststatus=2
, and hide = {alternate = true}
takes ~5 lines to add, so I figured why not.
What's the purpose of the
refocus
param forrender.update
? Not sure I understand what it fixes.
It allows freely-scrolling the bufferline via :BufferSrollLeft
/Right
. That command can be used to implement #68 when the time comes
Edit: #54 was the request
Let's use Squash & Merge to merge PRs (unless it's a large PR that's already formatted in clean commits, but that's rare).
@Iron-E a few questions:
config.options.hide
option really that useful? E.g. I see this line:if hide.alternate or hide.current or hide.inactive or hide.visible then
but I don't understand why users would hide those buffers.refocus
param forrender.update
? Not sure I understand what it fixes.