From: Philipp Kiefer <phil.kiefer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [FR] Add C-u and C-u C-u prefix arguments to org-paste-subtree (was: Make org-paste-subtree more predictable and useful)
Date: Fri, 20 Jan 2023 20:27:10 +0100 [thread overview]
Message-ID: <3a3f37a2-3e0d-06ce-4c86-ca3d73ed380f@gmail.com> (raw)
In-Reply-To: <875yd1tskz.fsf@localhost>
On 20.01.2023 11:21, Ihor Radchenko wrote:
> Philipp Kiefer <phil.kiefer@gmail.com> writes:
>
>> Further, you suggest I use C-S-<right> to demote the subtree after
>> pasting it at the same level as the subtree at point. But what if I used
>> a numerical prefix argument to copy or cut several subtrees, maybe 5 or
>> 10? Not very convenient at all to demote them all by hand...
>>
>> I still hold that pasting headings / subtress either at the same level
>> or at the child level of the target heading is part of the bread and
>> butter of outline editing and should be as straightforward as possible.
>> I'm rather sure the current numeric prefixes of org-paste-subtree to
>> select a distinct level at which to paste are needed / used much less
>> frequently than a "paste at child level" prefix (maybe C-u C-u?) would
>> be if it was implemented.
> Could you please provide concrete ideas what C-u/C-u C-u should do?
> In particular, how it will interact with point located at heading,
> at heading beginning, at empty heading, or inside a heading section.
To be honest, I don't see much need for fine-grained special cases. I'd
be very happy with C-u yanking at the level of the heading at point and
C-u C-u yanking at one level below that, regardless of the exact
position of point. I realize that would mean C-u doubling what can
already be done by calling org-paste-subtree with point at the beginning
of a heading but accessing both options (paste as sibling or child) with
a single or repeat C-u seems more consistent to me than having one
depend on position and getting at the other via the command prefix.
Thanks a lot for your dedication in working on this!
prev parent reply other threads:[~2023-01-20 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 20:14 Make org-paste-subtree more predictable and useful Philipp Kiefer
2023-01-18 8:04 ` Ihor Radchenko
2023-01-18 15:41 ` Philipp Kiefer
2023-01-19 9:44 ` Ihor Radchenko
2023-01-19 17:31 ` Philipp Kiefer
2023-01-20 10:12 ` [BUG] org-paste-subtree level when point is in the middle of a heading (was: Make org-paste-subtree more predictable and useful) Ihor Radchenko
2023-01-20 10:21 ` [FR] Add C-u and C-u C-u prefix arguments to org-paste-subtree " Ihor Radchenko
2023-01-20 19:27 ` Philipp Kiefer [this message]
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=3a3f37a2-3e0d-06ce-4c86-ca3d73ed380f@gmail.com \
--to=phil.kiefer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).