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 308774 - Dia saves backup files in homedir
Dia saves backup files in homedir
Status: RESOLVED DUPLICATE of bug 133863
Product: dia
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-23 13:35 UTC by Wouter Bolsterlee (uws)
Modified: 2005-10-15 14:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Wouter Bolsterlee (uws) 2005-06-23 13:35:17 UTC 
Dia saves backup files for unsaved files in the user's home directory. This is
really ugly on systems where Desktop == $HOME, because it clutters the desktop.
A cleaner solution would be to store the autosave files in $HOME/.dia.
Comment 1 Lars Clausen 2005-06-24 06:17:14 UTC 
It actually saves it in the current directory, which of course for most desktop environments mean 
$HOME ==  desktop.  The only other reasonable place for unsaved files would IMHO be $TMP.  
Nobody would think of looking in .dia if something crashes before they save the first time.
Comment 2 Alan Horkan 2005-06-24 12:36:38 UTC 
using the Currerent Working Directory (CWD) seems to be standard behaviour, even
Vim does it although it has an obscure configuration option that allows you to
use $tmp rather than $cwd

As so many other applications I would not want to change the default and make
Dia the odd one out but a hidden option that allowed advanced users to configure
it by editing a text configation file wouldn't be a bade idea.
Comment 3 Wouter Bolsterlee (uws) 2005-06-24 14:50:30 UTC 
Vim uses hidden files that don't clutter your desktop. So, .autosave.dia  would
be safe? Dia can notify a user on startup if a autosave file was found (just
like vim does).
Comment 4 Hans Breuer 2005-10-15 14:03:21 UTC 
*** Bug 133863 has been marked as a duplicate of this bug. ***
Comment 5 Hans Breuer 2005-10-15 14:05:48 UTC 
The duping should have been the other way around. Sorry about the noise.

*** This bug has been marked as a duplicate of 133863 ***