geeqie writes its own configuration files on every shutdown, independent
of need. when the user home resides on a not-so-fast storage (say,
network mounted, or, in my case, the sd card main disk of a media pc),
this can take up to a second, and even cause xfce4's "application is not
responding, shall i kill it?" screen to flicker over the screen.

this could be easily remedied by any of (and ideally all of) only saving
on demand, and by reacting to the user request even if there is
unfinished business (ie. close the window even before everything is
written to disk). thus, responsiveness could be restored.

note that this is semi-related to bug#623993: history would probably
have to be stored on every shutdown, so only the second part of the
solution also works there. (and still, it should go to .local/share).

best regards
chrysn