From: Allen Li <darkfeline@felesatra.moe>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Bug: org-paste-subtree displaces folded content [9.1.6 (9.1.6-48-gfe7619-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20180212/)]
Date: Fri, 16 Feb 2018 03:18:22 +0000 [thread overview]
Message-ID: <CAJr1M6dUntvm7o=jN9MPcP6a=nH7zEv3N9Xxa1RiSkS=CSjSkw@mail.gmail.com> (raw)
In-Reply-To: <87a7wahsr1.fsf@nicolasgoaziou.fr>
On Thu, Feb 15, 2018 at 1:02 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
> Allen Li <darkfeline@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?
I modified the example a bit and made the undesired behavior unclear.
* foo
:PROPERTIES:
:ID: a
:END:
* bar
:PROPERTIES:
:ID: b
:END:
Folded, this looks like
* foo...
* bar...
With point on the f in foo, press C-c C-x C-w. With point on the b in bar,
press C-c C-x C-y. Results in
* bar
* foo...
Unfolded, this looks like
* bar
* foo
:PROPERTIES:
:ID: a
:END:
:PROPERTIES:
:ID: b
:END:
I would expect C-c C-x C-y to work like C-RET rather than M-RET, that is to
always append after the heading and body rather than splitting it.
> Is there any good solution to this problem?
> Regards,
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2018-02-16 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 23:04 Bug: org-paste-subtree displaces folded content [9.1.6 (9.1.6-48-gfe7619-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20180212/)] Allen Li
2018-02-15 21:01 ` Nicolas Goaziou
2018-02-16 3:18 ` Allen Li [this message]
2018-02-26 23:10 ` Nicolas Goaziou
2018-02-28 2:07 ` Allen Li
2018-02-28 8:25 ` Nicolas Goaziou
2018-03-01 7:52 ` Allen Li
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='CAJr1M6dUntvm7o=jN9MPcP6a=nH7zEv3N9Xxa1RiSkS=CSjSkw@mail.gmail.com' \
--to=darkfeline@felesatra.moe \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).