When reverting entire file from inside a codediff tabpage, the underlying file is correctly updated on disk. However, after leaving the codediff tabpage and returning to the regular buffer, the buffer still shows the old contents.
Running:
causes the buffer to immediately reload and show the reverted contents.
Steps to reproduce
- Open a modified file in Neovim.
- Open it in codediff.
- Discard whole file changes from the codediff tabpage.
- Return to the regular buffer for that file.
- The buffer still shows the contents from before the revert.
- Run
:checktime.
- The buffer updates to the correct contents.
Expected behavior
After reverting changes through codediff, an existing buffer for the affected file should reflect the updated contents without requiring a manual :checktime.
For comparison, reverting the same file externally (e.g. through Lazygit in another terminal) is picked up automatically by Neovim and the buffer reloads as expected.
When reverting entire file from inside a codediff tabpage, the underlying file is correctly updated on disk. However, after leaving the codediff tabpage and returning to the regular buffer, the buffer still shows the old contents.
Running:
:checktimecauses the buffer to immediately reload and show the reverted contents.
Steps to reproduce
:checktime.Expected behavior
After reverting changes through codediff, an existing buffer for the affected file should reflect the updated contents without requiring a manual
:checktime.For comparison, reverting the same file externally (e.g. through Lazygit in another terminal) is picked up automatically by Neovim and the buffer reloads as expected.