From: Marcin Borkowski <mbork@mbork.pl>
To: "Peter Münster" <pm@a16n.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: disappearing lines
Date: Mon, 16 Jan 2023 21:24:52 +0100 [thread overview]
Message-ID: <871qnukz1n.fsf@mbork.pl> (raw)
In-Reply-To: <878ri26ztj.fsf@a16n.net>
On 2023-01-16, at 20:31, Peter Münster <pm@a16n.net> wrote:
> On Mon, Jan 16 2023, Arash Esbati wrote:
>
>> You can check your last keystrokes with `C-h l':
>
> This is not so easy, it works only in the same emacs session.
> Last time, I've discovered the disappearance of the lines 9 days later.
> I make daily backups, so I've used the diff between backup of 9 days ago
> and 8 days ago, to restore my file. It's annoying, because it's a very
> big file, with all things that I need to remember. About 20k lines.
> And about 300 lines have vanished...
> I would really like to understand, how this could happen...
I know that won't help you /right now/, but I had similar problems in
the past, and I pretty much got rid of them by commiting all my Org mode
files to Git every day (well, almost every day - my average over the
last 640 days is 0.90 times per day, although I'm getting closer to 1
recently). It would be great if Org mode had some way to warn me when
I delete something that is invisible (or undo in invisible parts of the
buffer), but I know of no such feature, so I do what I do. It takes
literally a minute or two every day, and I find it a very useful habit.
Hth,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-01-16 20:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 13:19 disappearing lines Peter Münster
2023-01-16 14:42 ` Panagiotis Koutsourakis
2023-01-16 16:57 ` Arash Esbati
2023-01-16 19:31 ` Peter Münster
2023-01-16 19:46 ` Jean Louis
2023-01-17 6:50 ` Peter Münster
2023-01-17 15:00 ` Jean Louis
2023-01-16 20:24 ` Marcin Borkowski [this message]
2023-01-16 21:14 ` H. Dieter Wilhelm
2023-01-17 1:11 ` Samuel Wales
2023-01-17 6:56 ` Peter Münster
2023-01-17 19:47 ` H. Dieter Wilhelm
2023-01-17 8:20 ` Panagiotis Koutsourakis
2023-01-17 11:28 ` Peter Münster
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qnukz1n.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=pm@a16n.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.