From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-orgmode@gnu.org
Subject: Re: Org suggestion: option which allows moving subtrees freely
Date: Tue, 11 Aug 2009 14:04:50 +0200 [thread overview]
Message-ID: <87prb2a74t.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: loom.20090811T103236-821@post.gmane.org
PT <spamfilteraccount@gmail.com> writes:
Hi!
>> So it would spare at least an M-left for the user which doesn't seem
>> much, but small things add up in the long run.
>>
>
> Maybe the M-right part wouldn't be too hard either. If above the moved
> up header (which is now at the same level as its previous parent
> header after an automatic M-left) there is an other header on the same
> level then it could be put under it with an automatic M-right.
>
> It could spare 2 keypresses which would be a real improvement.
I can't see that this would be a big improvement. If you want to move
the subtree that far away that the number of keystrokes invoced makes a
difference, then probably you should have used refiling in the first
run.
At least I'm one of those that would accidentially destroy the document
structure with such an automatic reparenting. ;-)
Well, as optional feature I don't have an opinion. But I think you
could add an around advice to `org-metaup' to get that behavior. Simply
ad-do-it and catch a possible error. If there was none, you are ok. If
there was one, you have to call `org-metaleft' followed by `org-metaup'
again.
Bye,
Tassilo
next prev parent reply other threads:[~2009-08-11 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 9:24 Org suggestion: option which allows moving subtrees freely PT
2009-08-11 9:36 ` Scot Becker
2009-08-11 9:56 ` Carsten Dominik
2009-08-11 10:12 ` PT
2009-08-11 10:35 ` PT
2009-08-11 12:04 ` Tassilo Horn [this message]
2009-08-11 9:57 ` Eric S Fraga
2009-08-11 9:57 ` Giovanni Lanzani
2009-08-11 12:15 ` Leo
2009-08-11 13:09 ` Matt Lundin
2009-08-11 13:24 ` Carsten Dominik
2009-08-11 16:05 ` Scot Becker
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=87prb2a74t.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.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).