Hello, Allen Li <darkfel...@felesatra.moe> writes:
> With the org file: > > * foo > some content > * bar > some content 1 > some content 2 > > 1. C-s foo RET > 2. C-c C-x C-w > 3. C-r some RET > 4. C-c C-x C-y > > Final content is > > * bar > some content 1 > * foo > some content > some content 2 I can reproduce it. > The behavior is insidious when the contents are folded: > > * foo... > * bar... > > turns into > > * bar... > * foo... IIUC, you cannot reproduce the example above when contents are folded, since you do not have access to the headline contents. > This can displace property and logbook drawers, timestamps, etc with very > little visual indication. > > Is this behavior even desirable? To me, killing and yanking subtrees > should keep the content with the headings and not "splice" subtrees into > the middle of another heading's content But you did yank the contents of the subtree into the middle of another heading's content. So, what should do Org? Decide that you don't know what you are doing and paste it at the end of the current section? What if you really want to split the current section? Is there any good solution to this problem? Regards, -- Nicolas Goaziou
