Hello, I had already written to you about LIBREoffice backups and you gave me a very good answer about what LIbreoffice recovery does in the event of a machine crash. After several disconnections from my linux session, I noticed that libreoffice backed up and offered to repair closed files without backup. Although I have set the LIbreoffice backup to 1mn, some sentences are missing, because what has not been saved by libreoffice is lost. I type quickly. I have to do, in addition, all the time, a CTRL + S. It's too heavy. So, I looked for text editors that record in real time. I found GEANY which records per second and immediately. No need to do CTRL + S anymore But it's not a text editor. No .DOC or .DOT or even .RTF. It does .TXT. There is an editor who does RTF, DOC and DOCX, it's JARTE. It records in real time but down to the minute. But at least it's really saved. No need to do CTRL + S. Can you make LIBREOFFICE capable of recording per second or 10 seconds in real time, so that nothing is lost. At least during the 10 seconds. It would be a big step forward. The recovery will be used after if the real-time recording has failed. Regards,
I think that is not possible for long document if the time necessary to save the file is bigger than a small part of a second. Best regards. JBF
(In reply to Aldebaran from comment #0) > I had already written to you about LIBREoffice backups and you gave me a > very good answer about what LIbreoffice recovery does in the event of a > machine crash. See bug 141827 > Can you make LIBREOFFICE capable of recording per second or 10 seconds in > real time, so that nothing is lost. This is not going to fly. I see two solutions: you write the text with Geany (or any other light-weight text editor) and format finally with LibreOffice. Or you investigate what causes the trouble. I assume it's a combination of weak hardware and heavy usage. Using a master document with smaller sections could help, less formatting, no redlining, no comments, etc. too. Images, charts, complex layouts use resources - use it sparingly and ideally at very last. And to not only blame your machine and workflow, we have to make sure to not crash in any case. But it's hard to find the remaining issues. I'm missing a note on the version but from the other ticket it seems to be 7.0.4. Please update to the latest still/fresh version - developers put a lot effort in stability and performance.