emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Samuel Wales <samologist@gmail.com>
To: Martin Pohlack <mp26@os.inf.tu-dresden.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unhiding edited areas
Date: Thu, 30 Jul 2009 11:10:13 -0700	[thread overview]
Message-ID: <20524da70907301110m208bc575jc1f18de4460cc56e@mail.gmail.com> (raw)
In-Reply-To: <4A71BF50.2050401@os.inf.tu-dresden.de>

Hi Martin,

This is a huge issue.[1]

Here is what I do to try to work around it.

I use git, to limit the damage from confusion.

I expand the entire buffer if I think I am about to be confused.

;;i like the idea of clustering undo but find it disconcerting
(setf org-self-insert-cluster-for-undo nil)
;;somebody, I think Carsten, suggested this, and it might work for
you, but for some reason I commented it out.  I don't remember what
the reason was.  Maybe speed.
'(defadvice undo (after org-undo-reveal activate)
 "Make point and context visible after an undo command in Org-mode."
 (and (org-mode-p) (org-reveal)))
;;(ad-unadvise 'undo)


[1]  It is even more important when combined with what is IMO Emacs's
greatest need for improvement, which is that you can undo, and undo an
undo, and this is considered to be sufficient since you can get
anywhere in the timeline in principle -- but many users, myself
included, prefer a true redo command, both because undoing an undo
does not let you do commands (such as copying) in the middle of an
undo sequence without going the other direction, and because it feels
more intuitive to tell emacs where in the timeline we want to go, and
go forward or backward if we overshoot, thus making it possible to
view the timeline the same way as we go backward and forward in any
linear sequence.  (redo.el provides the functionality, but it corrupts
the buffer.)  Of course, many are comfortable with the traditional
undo-the-undo mechanism, so that should stay possible, but there are
many who are not, and a redo mechanism would satisfy them.  It is
possible to get more fancy with a tree.

-- 
Myalgic encephalomyelitis makes you die decades early (Jason
et al. 2006) and suffer severely.  Conflicts of interest are
destroying research. What people "know" is wrong. Silence = death.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm

next prev parent reply	other threads:[~2009-07-30 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 15:42 Unhiding edited areas Martin Pohlack
2009-07-30 17:44 ` Eric S Fraga
2009-07-30 18:10 ` Samuel Wales [this message]
2009-07-30 18:50   ` Martin Pohlack
2009-07-30 20:23     ` Samuel Wales
2009-08-03 13:53     ` Carsten Dominik

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=20524da70907301110m208bc575jc1f18de4460cc56e@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mp26@os.inf.tu-dresden.de \
    /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

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