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 611765 - gimp shouldn´t save if no changes were made
gimp shouldn´t save if no changes were made
Status: RESOLVED INVALID
Product: GIMP
Classification: Other
Component: General
2.6.7
Other Linux
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 646105 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-03-04 02:41 UTC by felipemoraesbr
Modified: 2011-03-29 15:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description felipemoraesbr 2010-03-04 02:41:51 UTC
It would just be more convenient. It could display a message below: "No changes were made since opened or saved".
Comment 1 Sven Neumann 2010-03-04 07:56:59 UTC
Easy enough, just set "trust-dirty-flag" to "yes" in your gimprc. Please check the documentation and/or ask on the gimp-user mailing-list before filing a bug-report. This is not a help forum.
Comment 2 felipemoraesbr 2010-03-05 01:27:48 UTC
I acknowledge I posted this at the wrong place, since it was my first time trying to make gimp better. In another misplaced "bug report" they helped me saying the correct place to post these ideas.

Did you said i should do additional configuration? It would be better for gimp to have this behavior by default. An artist shouldn´t have to configure text files ever. I wasn´t asking help, I was giving an idea, but clearly it wasn´t the right place as it was told me recently.

Oh well, i just saw priority was set to normal? sorry again, I thought I set it to minor/trivial.

But thanks for the quick reply, please do not reply to this comment.
Comment 3 Sven Neumann 2010-03-06 14:04:24 UTC
We changed this in purpose not to be the default. And the discussion about this can be found in the mailing-list archives. Please stop discussing this in a closed bug report.
Comment 4 Michael Natterer 2011-03-29 15:05:27 UTC
*** Bug 646105 has been marked as a duplicate of this bug. ***