From: Samuel Wales <samologist@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: undo-tree and Org visibility
Date: Wed, 27 Feb 2013 10:58:15 -0700 [thread overview]
Message-ID: <CAJcAo8tFU5tWHKsrDRj1nOuYhbbep_dgbqLcjEspwQrBDACqBQ@mail.gmail.com> (raw)
In-Reply-To: <878v69r7sn.fsf@bzg.ath.cx>
Hi Bastien,
On 2/27/13, Bastien <bzg@altern.org> wrote:
> My suggestion here is to use M-x show-all RET (or Org cycling)
> before playing around with `undo-tree-undo' or `undo-tree-visualize'.
>
> You will then have a clear view of what is un-done,
> without the need to worry about the visibility state.
Correct me if I'm wrong, but M-x show-all is equivalent to my
defadvice (even worse because it shows more). Cycling will work
initially, but that will change as soon as some changes in body text
forces revealing that entry.
Finally, this requires careful consideration of when to do undo and
redo, and preparation beforehand, while I'd prefer those to be
natural, quick operations that do not require setting visibility
manually first.
The "clear view" is only a clear view if you have all of the headlines
showing. They will not show unless you have a very tall screen or
very small fonts or a very small amount of body text.
If you do not show the following headlines because the body text is
too long, then you cannot easily tell that the operation was a move.
Not saying anybody is interested, but I wanted to make the problem clear.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. ANYBODY
can get it. There is no hope without action.
next prev parent reply other threads:[~2013-02-27 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:52 undo-tree and Org visibility Samuel Wales
2013-02-27 17:22 ` Bastien
2013-02-27 17:58 ` Samuel Wales [this message]
2013-02-27 22:35 ` Bastien
2013-02-28 7:01 ` Samuel Wales
2013-02-28 7:46 ` Bastien
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=CAJcAo8tFU5tWHKsrDRj1nOuYhbbep_dgbqLcjEspwQrBDACqBQ@mail.gmail.com \
--to=samologist@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@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.
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).