-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
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
Fern may wrongly overwrites a non-fern buffer. #514
Labels
bug
Something isn't working
Comments
I'll check it after Vimconf. Let me know if I forget about this issue. |
OK 👍. Please don't mind, I don't think this is a critical issue; this rarely happens and we can restore the previous buffer contents with undo ;). |
@lambdalisue ping |
I could reproduce the issue but it seems a bit complicated... |
Seems to be working really well 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Fern wrongly overwrites a new, non-fern buffer in certain situation.
Reproduce steps
repro.vim
vim -u repro.vim
Environment
The cause of this bug
split
command at line 2 ins:repro
function, fern's auto duplication feature will create new fern buffer and trigger asynchronous viewer draws. At this time, the draws are not done yet and the new buffer is empty.enew
command at line 3 ins:repro
function opens a new empty buffer. However, sinceenew
reuse the current buffer if it's not modified, the current buffer will be a non-fern buffer with keeping its bufnr same to one that the previously created fern buffer had.(EDIT: Fix buffer positions in figures)
The text was updated successfully, but these errors were encountered: