You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be related to some autocommand not being triggered, e.g. when going through Ctrl-P and the buffer is dimmed in another tab etc already: when being displayed it is still dimmed. set cc=80 fixes this.
We might be able to detect this with e.g. another autocommand on CursorHold, which could be used for debugging in general, too: add a note in case the current buffer is not the expected one.
The text was updated successfully, but these errors were encountered:
I noticed the buffer not changing (remains in inactive state) when the buffer number is #1. All the other buffers work. I can close the #1 buffer to have the plugin work as expected. I can reopen the first buffer (vim uses the original buffer id), and watch the bug appear again.
Furthermore, when I restart vim and load a previously saved session, the bug fires up again with the buffer with the lowest buffer id.
This might be related to some autocommand not being triggered, e.g. when going through Ctrl-P and the buffer is dimmed in another tab etc already: when being displayed it is still dimmed.
set cc=80
fixes this.We might be able to detect this with e.g. another autocommand on CursorHold, which could be used for debugging in general, too: add a note in case the current buffer is not the expected one.
The text was updated successfully, but these errors were encountered: