emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dmitry Knyaginin <d.knyaginin@gmail.com>
To: Dmitry Knyaginin <d.knyaginin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Content below current line lost
Date: Mon, 15 Feb 2021 13:21:21 +0100	[thread overview]
Message-ID: <CA+GTVAhCi6dj1CsYCORch3aGP+ao6b-sAkq4FCooZKYpLer=hw@mail.gmail.com> (raw)
In-Reply-To: <87wnv97ebc.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

> if you invoke a special mode while visting a file not intended for that
> mode

sound interesting to test... in my case the file has been in org mode from
the beginning, and to be honest I am unsure I understand "not intended for
that mode". I mean, if I visit plain text files, I guess it does not matter
which mode I invoke, right?

About git -- totally. It's just that unexplained bugs add to the paranoia

By the way, I have started to test my theory that the bug has to do with
the file size, but so far I have not been able to reproduce the bug.

/ Dmitry

On Mon, Feb 15, 2021 at 12:36 PM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> On Friday, 12 Feb 2021 at 11:29, Dmitry Knyaginin wrote:
> > I have some wild theories, including a gamma particle hitting my laptop
> ;)
> Something I saw on the emacs developer list: if you invoke a special
> mode while visting a file not intended for that mode, it is possible for
> contents to be deleted and no undo information kept.  I don't have more
> details than this unfortunately.  Luckily, I've never run into this but,
> then again, I don't usually invoke a mode switching command explicitly.
> I'm glad you could get some (all?) of what you lost from git.  Another
> data point pushing everybody to use version control systems!
> --
> : Eric S Fraga via Emacs 28.0.50, Org release_9.4.4-213-g49364f

[-- Attachment #2: Type: text/html, Size: 2042 bytes --]

  reply	other threads:[~2021-02-15 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 10:57 Content below current line lost Dmitry Knyaginin
2021-02-11 16:24 ` Eric S Fraga
2021-02-12 10:29   ` Dmitry Knyaginin
2021-02-15 11:36     ` Eric S Fraga
2021-02-15 12:21       ` Dmitry Knyaginin [this message]
2021-02-15 12:45         ` Ihor Radchenko
2021-02-15 12:57           ` Dmitry Knyaginin
2021-02-15 12:54         ` Eric S Fraga

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:

  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='CA+GTVAhCi6dj1CsYCORch3aGP+ao6b-sAkq4FCooZKYpLer=hw@mail.gmail.com' \
    --to=d.knyaginin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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