Closed Iron-E closed 1 year ago
@otavioschwanck this is ready to try, I've refactored it. I've got a little more to do, and then I'll mark it for review before a merge
@otavioschwanck this is ready to try, I've refactored it. I've got a little more to do, and then I'll mark it for review before a merge
the current version is still not working.
Runned :Ex with two buffers Tried BufferNext:
Same with BufferPrevious.
It happens on the second time when opening the :Ex
the current version is still not working.
That was the "little more to do" I had, unfortunate coincidence you ran into that while I hadn't guarded against that edge case :smile: . 8db3e9d1b41eab31bc8819bb3cbf8334aca7e945 was specifically made to address that
@otavioschwanck double checking that this works for you before merging
Closes #367.
This PR adds a fallback for when a buffer is not found in the
state.buffers
list, and the:BufferNext
/Previous
command is run:state.buffers
(asstate.buffers
only lists valid, non-excluded buffers); orstate.buffers[1]
Fallback incidents are logged using
vim.notify
at log levelINFO
. It is possible to override thevim.notify
function to filter messages below a certain log level.