Closed acarl005 closed 4 months ago
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error
[ ] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
[ ] README
is properly formatted and uses fenced in links with <url>
unless they are inside a [title](url)
[ ] Proper usage of opts
table rather than setting things up with the config
function.
Map
[b
and]b
to the bufferline-specific calls for cycling buffers.📑 Description
I included
astrocommunity.bars-and-lines.bufferline-nvim
and observed the]b
and[b
bindings not behaving correctly. They were switching buffers, but out-of-order w.r.t. how they were displayed in bufferline. This PR remaps those to call bufferline's specific API for cycling through tabs. With this custom binding added, I now observe the correct behavior.ℹ Additional Information
It's not super straightforward to repro. Sometimes, I open a project, open various buffers, and press
]b
and the ordering is correct. Other times, after opening some buffers, say withgd
or from telescope searches, the buffer navigation starts happening out of order.