From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: Rainer Stengele <rainer.stengele@online.de>, emacs-orgmode@gnu.org
Subject: Re: org-indent-mode corrupted most of a big org file
Date: Mon, 2 Dec 2013 13:06:28 +0100 [thread overview]
Message-ID: <1768B7D8-D6EF-4C16-B9FD-D252E73142F0@gmail.com> (raw)
In-Reply-To: <861u1vzdyl.fsf@somewhere.org>
On Dec 2, 2013, at 12:31 PM, Sebastien Vauban <sva-news@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
>
next prev parent reply other threads:[~2013-12-02 12:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 11:21 org-indent-mode corrupted most of a big org file Rainer Stengele
2013-12-02 11:31 ` Sebastien Vauban
2013-12-02 12:06 ` Carsten Dominik [this message]
2013-12-02 15:37 ` Alexander Baier
2013-12-02 19:11 ` Nicolas Richard
2013-12-03 8:33 ` Johann Spies
2013-12-03 12:58 ` Alexander Baier
2013-12-03 17:23 ` Johann Spies
2013-12-03 17:37 ` Alexander Baier
2013-12-03 17:43 ` Nick Dokos
2013-12-03 17:53 ` Alexander Baier
2013-12-03 18:30 ` Nick Dokos
2013-12-03 19:29 ` Sebastien Vauban
2013-12-04 9:43 ` Alexander Baier
2013-12-03 18:15 ` org-indent-mode corrupted most of a big org file (solved backups) Johann Spies
2013-12-06 14:41 ` org-indent-mode corrupted most of a big org file Johann Spies
2013-12-07 10:48 ` Alexander Baier
2013-12-04 8:25 ` Nicolas Goaziou
2013-12-04 11:26 ` Rainer Stengele
2013-12-04 13:16 ` Nicolas Goaziou
2013-12-12 14:48 ` Rainer Stengele
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1768B7D8-D6EF-4C16-B9FD-D252E73142F0@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@online.de \
--cc=sva-news@mygooglest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).