https://bugs.documentfoundation.org/show_bug.cgi?id=160769
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTABUG |--- Ever confirmed|0 |1 Status|RESOLVED |REOPENED --- Comment #6 from [email protected] --- (In reply to Justin L from comment #4) > Quoting from bug 57414 comment 22: > > There are three types of Recovery. One is emergencySave (an exception in the > program triggers a save-and-restart), another is SessionSave (when the OS > shuts down), and the third is a timed autoRecovery. > > In the case of EmergencySave and SessionSave, the intent is to recover the > working environment, so ALL documents are attempted to be recovered. > > In the most general case (the timed autoRecovery) the patches only try to > recover modified documents that have a recovery file. > > > So, I tend to agree with Mike in comment 1 and the request to specifically > do it this way in bug 148438. In response to OP, I'd say that recent > documents exists to find those documents easily, so I don't see how > re-opening documents manually could be a problem. > > In general, it is not a good idea to have lots of documents open, so having > LO "recover" the entire last environment would not be smart and encourage > bad behaviour. In this case LO itself has no idea why it is restarting, so > it is best to just recover modified-but-not-saved files. That suggests that there is a bug here? If emergencySave is supposed to recover everything, and after a crash it doesn't, then clearly it crashed in such a way that it did not have a chance to do so, and is depending upon the timed autoRecovery instead? So there's a bug, just not the one from the original post. It still seems like it would be more prudent to give people the choice. An overlapping layer of reliability. The recent documents list is often not long enough, and organizes based on time originally opened, not which documents were recently used. If your work involves opening and closing a bunch of incoming documents or supplier sheets throughout the day, but not working with them, and instead working within other documents that are left opened longer - then it will not have useful files in the list. At the end of the day it's your choice as the developers/maintainers, but I would encourage you to think of users that are in the business world and not in the programming or home use world. It may be bad behaviour, but it's exactly how many businesses work, like restaurants. Another option if this is very unappealing, would be to create a "recently saved" list - as this type of user has no use for recently opened documents, and only cares about the ones that they are saving. The priority is completely opposite to how Justin outlined. Work sheets and supplier pricing updates and whatnot can just be redownloaded/reopened from email, but the documents opened for a long time are actually the priority. Those ones are the ones that are sometimes ignored by auto recovery and the recents list, depending on saving behaviour and how long ago they were originally open. Just food for thought, but I think they could be good changes to broaden the appeal to different types of users and use cases. -- You are receiving this mail because: You are the assignee for the bug.
