Bug 103234

Summary:	Periodical save to protect from crash
Product:	[Applications] kate	Reporter:	elonen
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	autoquote1000, bugzilla, mlemos, tim, wstephenson
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description elonen 2005-04-04 22:06:10 UTC

Version:            (using KDE KDE 3.3.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

It would be nice if Kate saved its' buffers periodically like OpenOffice.org, for example, does. Then, when it was restarted after a crash and it detected that a snapshot file existed, it would ask if the user wants to resume from the last saved state.

Please note that this is *not* the same thing as backuping a file before overwriting it -- autosave has indeed been requested before, but it has been dismissed as a duplicate of the now implemented overwrite-backup.

Comment 1 Dominik Haumann 2005-04-04 22:26:17 UTC

As some time ago it happened to me that I lost much data because of a crash I think this is a valid wish ;)

Comment 2 Greg Martyn 2006-05-22 06:00:25 UTC

This would be especially useful for files that haven't been saved yet.

Comment 3 Thomas Friedrichsmeier 2007-12-07 13:55:13 UTC

*** Bug 123937 has been marked as a duplicate of this bug. ***

Comment 4 Thomas Friedrichsmeier 2007-12-07 13:59:48 UTC

*** Bug 38974 has been marked as a duplicate of this bug. ***

Comment 5 Maciej Pilichowski 2007-12-31 11:36:14 UTC

I would like to add my 2 cents by stressing the design of this feature. Commonly it is referred as autosave or autobackup. The first name is a bit misleading, editor should not automatically "save" the date, but just make a backup (automatically). So it there is a file:
a.txt
and I would edit it in Kate (autobackup set), Kate should create periodically backups
a.txt.backup (just an example)
but a.txt should remain intact until the user explicitly hit "save".

Sorry it this was obvious from the beginning but I thought I better comment this then post a wish "please change the behaviour..." :-))

Comment 6 charles 2008-04-27 01:58:43 UTC

I have, several times in the last several weeks, had my computer crash/shut-down while i was working.  The last few were due to the power switch being hit by a chair, the cat lying down on my keyboard, and a system error causing shutdown.  Each time i was able to restart firefox with the session automatically restored, restart thunderbird where i left off, but several days worth of unsaved notes in kate were lost.  This is not tolerable.

Comment 7 Darek 2008-11-28 04:41:20 UTC

I agree, no autosave option in Kate is terribly annoying... The same happened to me today when my laptop crashed (turned off suddenly), as I suppose because of overheating... I has been working on my document for 4 hours before and all that is gone. Please, do something about autosave!

Comment 8 Thomas Friedrichsmeier 2009-09-06 10:49:21 UTC

*** Bug 144694 has been marked as a duplicate of this bug. ***

Comment 9 Thomas Friedrichsmeier 2009-09-06 10:49:46 UTC

*** Bug 205906 has been marked as a duplicate of this bug. ***

Comment 10 Will Stephenson 2010-09-29 17:13:48 UTC

Is this fixed in 4.6 by dianat's work?

Comment 11 Janet 2010-09-29 20:03:31 UTC

I don't use kate but its little brother kwrite. Kwrite also needs that autosave feature. Does it automatically profit from an autosave feature implemented in kate?

Comment 12 Milian Wolff 2010-09-29 20:11:18 UTC

fixed for KDE 4.6 indeed, thanks for the heads up.

@ Janet: Every user of Katepart (e.g. Kile, KDevelop, Kwrite, Kate, ...) will have this feature.