From: Samuel Wales <samologist@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Eric Schulte <schulte.eric@gmail.com>
Subject: Re: [bug] [babel] babel corrupts undo history
Date: Fri, 21 Mar 2014 17:37:14 -0700 [thread overview]
Message-ID: <CAJcAo8tNqMuPGyWKZhdY8S=W96B0W_socpo5T0QXc+Az=K4Q5w@mail.gmail.com> (raw)
In-Reply-To: <877g7njdak.fsf@bzg.ath.cx>
bug #3:
insert a source block
edit after it
c-c ' to edit
edit
c-c ' to go back to mybuffer
edit before the source block
undo
undo
you should notice that the source block is not restored.
note that this is not the same buffer corruption issue i reported previously.
in that one, you insert a source block, fill it, and undo. then the
next header line gets corrupted:
bug #2:
* header
#+begin_src org
asdf
asdf
#+end_src
* header2
put point inside the source block, fill, then undo. you will see
buffer corruption after the source block. the exact corruption
varies. sometimes it is removal of the #. other times it is removal
of * in 1 or 2 headlines below.
what makes it much worse is that you cannot undo to fix the buffer
corruption. you have to revert the buffer.
there are others. i believe the reason is that org tries to get fancy
with undo.
next prev parent reply other threads:[~2014-03-22 0:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 1:13 [bug] [babel] babel corrupts undo history Samuel Wales
2013-08-28 14:42 ` Eric Schulte
2013-08-28 16:03 ` Aaron Ecay
2013-08-28 18:52 ` Eric Schulte
2013-08-28 19:41 ` Samuel Wales
2013-08-28 19:43 ` Samuel Wales
2013-08-28 19:51 ` Samuel Wales
2013-10-28 19:17 ` Aaron Ecay
2013-10-28 19:45 ` Samuel Wales
2013-10-28 20:07 ` Aaron Ecay
2013-10-28 21:26 ` Samuel Wales
2014-03-10 2:46 ` Samuel Wales
2014-03-18 20:48 ` Bastien
2014-03-21 21:34 ` Samuel Wales
2014-03-21 22:07 ` Bastien
2014-03-21 22:42 ` Samuel Wales
2014-03-21 22:45 ` Samuel Wales
2014-03-21 23:40 ` Bastien
2014-03-22 0:11 ` Samuel Wales
2014-03-22 0:18 ` Bastien
2014-03-22 0:37 ` Samuel Wales [this message]
2014-03-22 0:44 ` Samuel Wales
2014-03-22 8:43 ` Bastien
2014-03-22 8:57 ` Samuel Wales
2013-08-28 17:08 ` Samuel Wales
2013-08-28 17:18 ` Samuel Wales
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='CAJcAo8tNqMuPGyWKZhdY8S=W96B0W_socpo5T0QXc+Az=K4Q5w@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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).