Skip to content
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

Closing the explorer says: No write since last change #522

Open
cpfaff opened this issue May 8, 2022 · 4 comments
Open

Closing the explorer says: No write since last change #522

cpfaff opened this issue May 8, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@cpfaff
Copy link

cpfaff commented May 8, 2022

Sometimes it happens to me that when I close the buffer of the explorer then it gives me the wraning "No write since last change". That might be caused as the explorer relies on the buffer being "modifyable" and sometimeds the changes may not yet written when I want to exit my editor.

@weirongxu weirongxu self-assigned this May 9, 2022
@weirongxu weirongxu added the bug Something isn't working label May 9, 2022
@weirongxu
Copy link
Owner

This issue does not seem to be stably reproduced, I suspect that some exceptions occur in nvim_buf_set_lines. I try to fix it by this patch 3992e5d

@cpfaff
Copy link
Author

cpfaff commented May 9, 2022

Just updated and tried again. I still see that message every now an then. However I guess it happens just in a really specific edge case. I had no time yet to figure out reliable steps to reproduce it. I am on it.

@cpfaff
Copy link
Author

cpfaff commented May 9, 2022

Sometimes it happens when i do this:

  1. Open vim in a project folder
  2. Open the explorer
  3. Open a file from the explorer
  4. Edit the file and save it
  5. :bd! close the file buffer
  6. Switch back to the explorer buffer
  7. :bd! close the explorer buffer
  8. Exit vim :q!

Then I get the warning. And when I then hit q then I end up in the explorer again

@weirongxu
Copy link
Owner

I guess other plugins have modified the coc-explorer buffer, then caused this issue. I have frequently encountered this recently, I will follow up on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants