emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org, Eric Schulte <schulte.eric@gmail.com>
Subject: Re: [bug] [babel] babel corrupts undo history
Date: Fri, 21 Mar 2014 23:07:49 +0100	[thread overview]
Message-ID: <87r45vkxxm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAJcAo8swSqkt=VJMnnh4yhG73xPZc5C1qgzV8sAxZSmtFXc9tA@mail.gmail.com>	(Samuel Wales's message of "Fri, 21 Mar 2014 14:34:51 -0700")

Hi Samuel,

Samuel Wales <samologist@gmail.com> writes:

> typical example of last one:
>
> ===
> * bastien
> #+begin_src org
>   bastien
>   ^bastien
> #+end_src
> * bastien
> ===
>
> put point at ^, fill-paragraph, undo.  with undo-tree, at least, the
> buffer will be corrupted.

Not for me.  This has surely to do with undo-tree.

> one thing org sometimes does is try to set buffer-undo-list.  it's
> really for speed imo.  i can't think of any reason why org really
> needs it.  perhaps i am mistaken and there is a really good reason for
> such things, but i suspect it has caused a lot of bugs.

I can safely say this is *never* for speeding things up, it's for
preserving the undo list state.

> in the case of c-c ', i would prefer having the indentation adding
> show up as an undo entry [or whatever would happen if we ripped out
> the undo-related setting].

Unless I misunderstand, the addition of indentation is not manually
done, so it should not be part of the undo list.  

> even when there is not a bug per se, when you edit a source block,
> there is a gap in the undo record.  like nixon's tape gap during
> watergate, it raises questions.  :/

:)

> to me, undo is a low-level feature that should never be buggy or
> surprising.  if it is, then anything that causes those should be
> ripped out, even if it means losing a fancy undo-related feature.

Fully agreed.  Let's raise bugs in this area when you have time
and when the bug can be isolated from other third-part package.
Maybe that's me not being able to reproduce the ones you mention,
but other people can chime in too, if the bug is real.

Thanks!

-- 
 Bastien

  reply	other threads:[~2014-03-21 22:08 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 [this message]
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
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=87r45vkxxm.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    --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).