Environment:
Win 10
Eclipse 2018-09
CIQ Plugin 3.0.6
Monkey C will not reset a dirty buffer to clean after undoing all changes.
Eclipse (and most text editors for coders) have two states for buffers: clean and dirty. Clean means that you have no unsaved changes, and dirty is the opposite. You can tell if a buffer is dirty in Eclipse by looking for the asterisk (*) to the left of the editor tab title. Eclipse will also prompt you to save changes if you try to close a dirty buffer.
Most editors, including the Eclipse C, Java and JavaScript editors, will reset a dirty buffer to clean if the user undos all changes. This is convenient because now the user knows there is nothing to save and no changes to be lost. Perhaps more importantly, when closing the app / tab, the user will not be prompted to save changes where none exist.
This also causes problems with source control (Git) tracking in Eclipse. If you undo all changes and the buffer remains dirty, the natural impulse is just to save the buffer. Now Eclipse thinks that your buffer has changed compared to the reference version in source control and will mark it as "modified", which is misleading. If this was working properly, then it would be impossible for this to happen, because you can't save a clean buffer in Eclipse.
Recreation Procedure:
- Open Eclipse
- Open MC file
- Note clean buffer state
- Type one thing
- Note dirty state
- Press CTRL-Z
- Note that buffer is still marked as dirty, even though the contents have been restored to the clean state.
Some other editors which handle this properly:
js, java and c editors in Eclipse
Notepad++
Sublime
Microsoft Word
Visual Studio 2010
vi