After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 396044 - gedit asks to save even when document is empty
gedit asks to save even when document is empty
Status: RESOLVED NOTABUG
Product: gedit
Classification: Applications
Component: general
2.16.x
Other Linux
: Normal minor
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-13 09:31 UTC by Josselin Mouette
Modified: 2009-01-10 14:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Josselin Mouette 2007-01-13 09:31:15 UTC
[ forwarded from http://bugs.debian.org/406696 ]

Gedit asks if I want to save the document even when it is empty.

For instance, if I open gedit, type a character, and then delete it,
and then try to close gedit, this happens.
Comment 1 robertojimenoca 2007-01-13 14:17:05 UTC
I do not see what is the problem with the current behavior.

Could you send a real use case where the current behavior could be a
problem instead of the silly one you posted?

Almost every other application has just the same behavior.
Are you sure you want to change all the applications to this new behavior?

Did you consider that also people would like to open a file remove all
its contents and save an empty file?
Comment 2 Josselin Mouette 2007-01-13 18:27:37 UTC
I personnally don't care a single microsecond about this issue. However it seemed a legitimate request to be forwarded here, as long as it doesn't affect valid uses.

I could understand if no one would want to work on this, as it's the same for me. In this case I can ask the submitter to provide a patch if he wants to see this change.
Comment 3 Paolo Borelli 2009-01-10 14:53:32 UTC
Once the document has been "touched" we cannot know how much value there is in the information that has been erased and that it is stored in the undo history, so we must prompt the user. The current behavior is correct.