Editor's "dirty" state does not reset when undoing all the way back
Reported by Charles Oliver Nutter | May 2nd, 2010 @ 07:24 PM
If you open a file, edit it, and undo that edit, it still shows as dirty in the tabs (filename prefixed with a *). In most editors, if you undo all changes back to the most recent save (or initial load), they will reset to "clean" state for the file.
This is important if you use that clean state to indicate when you have "undone enough" to be back to clean.
Comments and changes to this ticket
-
Charles Oliver Nutter May 2nd, 2010 @ 07:25 PM
It also still prompts you to save when you close the file.
-
Deleted User November 20th, 2010 @ 04:52 AM
- Milestone order changed from “0” to “0”
Someone seems to have fixed this wrong.
When you undo to the last save point, the dirty flag goes away.
When you undo PAST the last save point, the dirty flag remains gone. This is especially bad, since it is a potential data loser: you have a buffer that is not saved but says it is.Reproduce:
"delta 1" # Buffer is dirty # Buffer is clean
"delta 2 # Buffer is dirty # Buffer is clean
# Buffer is empty, should be dirty, but is marked clean -
Deleted User November 20th, 2010 @ 04:57 AM
Ratsenfratsen fail to preview.
Reproduce:
"delta 1" # Buffer is dirty SAVE # Buffer is clean "delta 2" # Buffer is dirty UNDO # Buffer is clean UNDO # Buffer is empty, should be dirty but is marked clean
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A programmer's text editor for Gnome.
Charles Oliver Nutter
The Doctor What