| Summary: | Auto save and safe save | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | mlemos |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | chanika, holger-kde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
mlemos
2002-03-05 01:54:57 UTC
*** Bug 46974 has been marked as a duplicate of this bug. *** now we create backup files since 3.1 since kate3.1 or kde3.1 ??? Hmmm... backups and auto-saving are different issues. So I don't agree in setting this wish to status "resolved", because up to V2.4.1 kate has no autosave feature. I would apprecciate a real autosave feature with configurable elapsed time or keystrokes. I must agree, the backup feature of Kate means you always have a copy of the previous save. However, if you keep typing for hours and hours and something happens, you loose all those hours of work. An autosave feature would protect you from this. Kile implements autosave, and it is quite different from the Kate backup features (which is also very essential I think). I'd say: reopen or mark as "won't fix". best, Jeroen why is this marked as "fixed"? I can't find any kind of autosave in kate. it just crashed again and I lost HOURS of work! for god's sake, almost every other text editor on the planet can do autosave, why can't kate? I'm mainly using it because of the good support for chinese characters - normally I use vim, which never EVER loses even a single character no matter how much abuse my computer takes. I was proud of not needing a ctrl-s nervous tick to protect my work. now I guess I'll have to develop one again until someone implements some autosaving... honestly, I wish I could find out how vim does it and add that to kate, but I just don't have the time. :( can someone please at least add a basic save timer? it can't be hard, can it? Oddly enough, I just griped on kdevelop-devel because they implemented their own autosave (when I am also of the opinion that it needs to be in KATE). FWIW don't expect this in KDE 3.x, but I agree KDE4 really ought to have an auto-save option. Note: the right way to do this is, as Chani suggests, similar to what Vim does: periodically auto-save to a temporary (probably hidden) file, and check for the existence of such a file when re-opening a document. A regular 'save' and/or 'close' deletes the temporary auto-saved file. Significant problem in using this otherwise excellent editor. All work is lost if system crashes. KOffice has implemented a very useful autosave feature which is indispensable. This should be a standard feature. just an observation: it appears that dcop has a way to close all files, but no way to save at all. so much for the idea of a simple dcop script for autosaving. next thing to find out is whether a plugin can do such a thing. it's about time I figured out how this plugin thing works anyways :) Marking this as a duplicate of bug #103234 . Yes, I know, this report is much older than the other, but 103234 contains only the remaining part of this wish (auto-save), which makes it easier to deal with. You may want to transfer your votes. *** This bug has been marked as a duplicate of 103234 *** |