From: Matt Lundin <mdl@imapmail.org>
To: David Maus <dmaus@ictsoc.de>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>,
Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-paste-subtree and org-refile broken
Date: Sat, 13 Aug 2011 09:03:40 -0500 [thread overview]
Message-ID: <87ty9lpfwj.fsf@fastmail.fm> (raw)
In-Reply-To: <877h6h4g2y.wl%dmaus@ictsoc.de> (David Maus's message of "Sat, 13 Aug 2011 15:05:25 +0200")
David Maus <dmaus@ictsoc.de> writes:
> At Sat, 13 Aug 2011 09:25:19 +0200,
> David Maus wrote:
>>
>> Hi Matt,
>> Hi Sebastien,
>>
>> I pushed a temporary workaround to master that should fix the problem
>> with refile and capture. Both depend on a buggy behavior of
>> org-paste-subtree, i.e. pasting a subtree *above* the target headline
>> when called with point at the beginning of the target headline.
>
> If you have already pulled, please pull again. Had confused something,
> fixed now.
Thanks for fixing this! Refiling is working well now. Could you explain
what you mean by a "buggy behavior of org-paste-subtree." AFAIK,
org-paste-subtree has always pasted the subtree above the current tree
if the point is at the beginning of the headline. Is there something in
the documentation that suggests that this should not be the case? I
believe this behavior is consistent with
org-insert-heading-respect-content, which inserts a new heading above
the current heading if called at the beginning of a headline. For
instance, in the following example...
--8<---------------cut here---------------start------------->8---
* One
Text in one
* Two
Text in two
** Subpoint two
Text in subpoint two.
* Three
Text in three
* Four
Text in four
--8<---------------cut here---------------end--------------->8---
If I kill headline four, move the point to the beginning of headline
three, and yank (i.e., call org-paste-subtree), I get the following,
which seems to me correct:
--8<---------------cut here---------------start------------->8---
* One
Text in one
* Two
Text in two
** Subpoint two
Text in subpoint two.
* Four
Text in four
* Three
Text in three
--8<---------------cut here---------------end--------------->8---
Similarly, if I place the cursor on three and call
org-insert-heading-respect-content (M-RET), the new headline is inserted
above the headline:
--8<---------------cut here---------------start------------->8---
* One
Text in one
* Two
Text in two
** Subpoint two
Text in subpoint two.
*
* Three
Text in three
* Four
Text in four
--8<---------------cut here---------------end--------------->8---
Best,
Matt
next prev parent reply other threads:[~2011-08-13 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 3:31 org-paste-subtree and org-refile broken Matt Lundin
2011-08-13 3:36 ` Matt Lundin
2011-08-13 7:25 ` David Maus
2011-08-13 13:05 ` David Maus
2011-08-13 14:03 ` Matt Lundin [this message]
2011-08-20 18:41 ` David Maus
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=87ty9lpfwj.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).