On Dec 2, 2013, at 12:31 PM, Sebastien Vauban <sva-n...@mygooglest.com> wrote:
> Rainer Stengele wrote: >> last week I played around with org-indent-mode in my biggest (37.000 lines) >> org file. >> 3 days later I detected that most of the file was corrupted. >> WHy so late? Using the agenda I only saw the todos and did not recognise the >> corrupted structures. >> Most "*" items had been placed at the beginning of the line and therefore >> now became headlines. >> I do not know how this happened. I am not sure if I myself was the reason >> somehow. >> Anyway I had to spend a fair amount of work to get the old file format from >> subversion and insert the changes since the corruption. >> >> This is just a warning to have backups at hand before changing to org-indent >> mode. >> Then immediately and check often the contents of the file until you are sure >> all is running well. >> >> Maybe someone has an idea. >> >> I will try to convert again later but then be much more careful. > > Last week, I also "lost" contents in the file I worked a lot in (R code, > published to slides). In fact, I did not really lose it, thanks to SVN... > > That seems to have been a nasty bug in the caching. I should be fixed AFAICT. > But, yes, this can always happen. Better to have fallback mechanisms when it > occurs -- even if we've to admit it is very, very seldsom, and only with the > dev trunk. This is great advice, in particular while testing fundamental changes like the caching mechanism. git-up everybody! - Carsten > > Best regards, > Seb > > -- > Sebastien Vauban >