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

Document dirty state is not correct if changes are undone after saving #122

Closed
solemnwarning opened this issue Feb 11, 2021 · 0 comments
Closed
Labels
Milestone

Comments

@solemnwarning
Copy link
Owner

Both the dirty and dirty_bytes members are left invalid if a change is undone after being saved. Results in the document potentially not being marked as unsaved and the wrong bytes being highlighted as changed.

Have a fix for this mostly prototyped, but there are some awkward edge cases I haven't decided how to resolve yet.

@solemnwarning solemnwarning added this to the 0.4.0 + 1 milestone Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant