[ jEdit-devel ] [Bug #127101] Using undo to max allows changed file to close w/o warning

Bug #127101, was updated on 2000-Dec-29 13:58
Here is a current snapshot of the bug.

Project: jEdit
Category: editor core
Status: Open
Resolution: None
Bug Group: normal bug
Priority: 5
Submitted by: jelvis
Assigned to : nobody
Summary: Using undo to max allows changed file to close w/o warning

Details: Java version:  jdk 1.2.2
jEdit version:  3.0 final
OS:  Windows NT 4.0, SP 6

Description:
   If you make at least undo limit + 1 changes to a file, then undo as many
as you can, you are left with a file that has changed since being saved,
but jEdit thinks it is not changed, so you can close the file without
saving it and not receive the warning about a buffer with unsaved changes.

How to duplicate:

1.  With jEdit started, go to Utilities->Global Options->Editing and set
the Number of Undos to 10 or some other small number.  (This is not
absolutely necessary, but it makes for a quicker test than the default of
100).
2.  Open a file and make 11 changes (assuming that 10 is the Number of
Undos - otherwise, just make 1 more change than you have undos).  I just
hit the space bar 11 times.
3.  Hit CTRL-Z (undo) 10 times (or until you can't undo anymore).  Now,
notice that the changed/not-changed indicator shows not changed (though
there is still an extra space), then attempt to close the file - it closes
without issuing a warning that it has been changed but not saved.

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=127101&group_id=588