We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From time to time I'm running into an issue where the highlights are out of place.
With the following screenshot they are correct on the left side, but not the right one:
The right window/buffer has been updated (via Neovim's W11: Warning: File … has changed since editing started. [O]K, (L)oad File).
W11: Warning: File … has changed since editing started. [O]K, (L)oad File
The left window/buffer is the one from before the update (the old Git checkout - I've changed branches, which updated the file).
As you can see the highlights from the left side (old/initial buffer) are also used on the right side (new/reloaded buffer).
I have the feeling that it might be related to using set noautoread in the first place, but could not reproduce it currently yet.
set noautoread
This issue is meant to track debugging of this for now.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From time to time I'm running into an issue where the highlights are out of place.
With the following screenshot they are correct on the left side, but not the right one:
The right window/buffer has been updated (via Neovim's
W11: Warning: File … has changed since editing started. [O]K, (L)oad File
).The left window/buffer is the one from before the update (the old Git checkout - I've changed branches, which updated the file).
As you can see the highlights from the left side (old/initial buffer) are also used on the right side (new/reloaded buffer).
I have the feeling that it might be related to using
set noautoread
in the first place, but could not reproduce it currently yet.This issue is meant to track debugging of this for now.
The text was updated successfully, but these errors were encountered: