Re: [O] org-paste-subtree and org-refile broken

2011-08-20 Thread David Maus
At Sat, 13 Aug 2011 09:03:40 -0500, Matt Lundin wrote: David Maus dm...@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

Re: [O] org-paste-subtree and org-refile broken

2011-08-13 Thread David Maus
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. A fix for

Re: [O] org-paste-subtree and org-refile broken

2011-08-13 Thread David Maus
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

Re: [O] org-paste-subtree and org-refile broken

2011-08-13 Thread Matt Lundin
David Maus dm...@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

[O] org-paste-subtree and org-refile broken

2011-08-12 Thread Matt Lundin
The following commit broke org-paste-subtree (and, as a result, refile): , | commit ece3091f16af246780e29ba6e8248dd8bb3b7ba2 | Author: David Maus dm...@ictsoc.de | Date: Wed Aug 10 18:38:26 2011 +0200 | | Don't eat headline when yank with point at existing headline | | *

Re: [O] org-paste-subtree and org-refile broken

2011-08-12 Thread Matt Lundin
Matt Lundin m...@imapmail.org writes: If I kill subtree Four and call org-paste-subtree with the point on Two (or if I refile it to Two), I get the following: * One Text in one * Two * Four Text in four Text in two * Three Text in three I should add that the correct result (and