if the save dialog closes and the application allows itself to also be closed--both without the save in progress completing fully, resulting in no save or a corrupted save and essentially a lost file and work... i would consider that a serious bug and report it as such.
Yeah, except GIMP heard of The principle of least astonishment and took it as a fucking challenge. If it astonishes you by behaving in an unexpected way, it's probably a deliberate GIMP design choice who's goal is to defy your expectations.
then i would probably duplicate the problem in a standard debian stable desktop install, and submit the bug report there. let them pester gimp.
OK hear me out, so I've been out drinking but I had this idea. You need to know when the save is done, right? Assuming you are on linux, you could use itnotify to alert you each time a save completes of your gimp files by ringing the console bell. Then you know you can't quit until you hear the bell.
I don't know if it would work. Maybe something like this
#!/bin/bash
# Target directory to watch (where the gimp files are)
WATCH_DIR="$HOME/Projects"
echo "Listening for completed GIMP saves in $WATCH_DIR..."
# Monitor for files closed after being written to
inotifywait -m -r -e close_write --format '%f' "$WATCH_DIR" | while read -r FILE
do
# Check if the modified file is a GIMP file (.xcf)
if [[ "$FILE" == *.xcf ]]; then
echo "Finished saving: $FILE"
# Trigger the system bell (or substitute with an 'aplay' command for a custom sound)
echo -e "\a"
fi
done
Calm down Satan.
GIMP
All about the GNU Image Manipulation Program • Please tag your help-me posts with [Help]. • YouTube Channel spamming will not be tolerated. • Blogspam will not be tolerated.