-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
feat: Integrate BufWriteCmd for "write" command #2116
Conversation
I found an edge behavior, not sure if this is intentional or a minor bug. If you make a change, then undo it, you are back to the last saved version but the vscode dirty status is still enabled. However, running |
This needs to be done in a separate PR. Once the document modifications are synchronized, updating this status will suffice. Additionally, even if a special circumstance causes the status to be incorrect, it's okay; it's not very important. |
I have updated the README. Please review |
close #2075