Community
Participate
Working Groups
To see the problem: Double-click on a resource to open an editor. Make some changes. Undo all the changes. Note that the '*' still appears by the name of the file in the editor tab, and that the Save button has not been greyed out. Many text editors provide visual confirmation that all unsaved changes have been undone by restoring whatever visual cues onscreen it uses to show that a file has been saved. This makes the current behaviour somewhat counter-intuitive by comparison. JB (30/05/2001 4:01:03 PM) NOTES:
PRODUCT VERSION: Build 113
Problem still exists in the 12/4/2001 Driver, and has been reported by one of our key customers.
Kai, Pls check in latest 2.0 builds.
problem still exists in 20020214 and 20020321 build
Post 2.0
*** Bug 7198 has been marked as a duplicate of this bug. ***
*** Bug 16236 has been marked as a duplicate of this bug. ***
*** Bug 12926 has been marked as a duplicate of this bug. ***
*** Bug 20516 has been marked as a duplicate of this bug. ***
*** Bug 21157 has been marked as a duplicate of this bug. ***
*** Bug 22022 has been marked as a duplicate of this bug. ***
Is anything going to be done for this bug? It was marked as later for 2.0, and here we are post 2.1 - just don't want it to fall through the cracks...
yes please do something about this.. it is very annoying.. I tried it myself to change the code. But the dirty state is of a Editor is completely separated from the Undo/Redo mechanism.. as far as i could see.
Now that we are well past 2.0, should this bug be re-opened?
Deferred for 3.0.
Is this going to be done for 3.0? This bug has been around since time immemorial - how hard could it be to fix? It is EXTREMELY annoying to have to close/reopen an editor just to get rid of an accidental edit, especially with all the prompting eclipse does when a buffer is dirty and you try to do anything. Every other substantial editor out there has this capability, and I'm sure I couldn't be the only one that this annoys so much. Is it just falling through the cracks because it is marked as resolved? If do, please reopen it - I really would like this to be in 3.0
yes please reopen this asap. this is long time a quite annoying thing. I already looked at the code for this but the undo/redo support is in a completely different portion of the code then the state of the editor (at least that's the way it looked to me quite some time ago when i looked at it)
reopening
oops... undoing last change
Hey, are you trying to pull a fast one here? ;-) As of 200406180800, this is most assuredly NOT fixed, so maybe you meant to change the status to something else?
moving back to LATER :-(
MVM was here ;-)
Just a thought on implementing this: Since QuickDiff(Revision on Disk) seems to be able to tell if an editor is clean (diff list is empty), why not just reuse that functionality to set the buffer's dirty flag after an undo operation?
Will there anything be done on this issue? It is a really annoying one.
You don't enjoy right-clicking and selecting "Revert" 10 times a day? That's odd :-)
Meehn, that's odd. Although there is the information about this available, it is not used at all.
Is this bug being ignored because it is marked Resolved? If no one says otherwise, I'll assume that is the case and create a new bug.
reopening for 3.1
/me does a little dance =)
For the next 3 years, or 36 months or 1071 days (and more)???
*** This bug has been marked as a duplicate of 21493 ***
