unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Peter Münster" <pm@a16n.net>
To: help-gnu-emacs@gnu.org
Subject: Re: disappearing lines
Date: Mon, 16 Jan 2023 20:31:52 +0100	[thread overview]
Message-ID: <878ri26ztj.fsf@a16n.net> (raw)
In-Reply-To: 86pmbe1kpt.fsf@gnu.org

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...

No, I don't have a cat, walking on the keyboard... ;)


> | To record all your input, use ‘open-dribble-file’.

I guess, that it would be very hard to find the bad keypress several
days later. There are no timestamps...

Best,
-- 
           Peter




  reply	other threads:[~2023-01-16 19:31 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878ri26ztj.fsf@a16n.net \
    --to=pm@a16n.net \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).