From: Bastien <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Adam Porter <adam@alphapapa.net>, emacs-orgmode@gnu.org
Subject: Re: Provide org-insert-subitem
Date: Mon, 25 Dec 2023 10:14:30 +0100 [thread overview]
Message-ID: <87y1dive2x.fsf@gnu.org> (raw)
In-Reply-To: <87edfoq16o.fsf@localhost> (Ihor Radchenko's message of "Thu, 14 Dec 2023 15:00:15 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
>> S-RET already "copy down" a table cells, so I'm really suggesting a
>> generalization of the current keybinding.
>
> This makes sense.
>
>> - S-RET on a list item calls `org-insert-subitem`, a new command.
>
> Did you mean `org-clone-item'?
Yes, sorry (`org-clone-item' is better than `org-item-copy-down', the
other idea that comes naturally.)
>> - C-M-RET on a heading calls `org-insert-subheading', the existing
>> command.
>>
>> - C-M-RET on a list item calls `org-insert-subitem', a new command.
>>
>> I like C-M-RET better than S-RET because inserting a subheading is
>> like a "subkey" or inserting a heading.
>
> I tried to play around a bit with various flavours of X-<RET> commands
> and I am not sure if I like C-M-RET:
>
> 1. For org-insert-heading, we have multiple variants that allow
> inserting heading at point, after current subtree, and the same
> variants for TODO heading. We don't have enough key combinations left
> to allow all the equivalents for subheadings.
>
> 2. With `org-cycle-level-after-item/entry-creation' set to t (default),
> it is actually very easy to create a subheading/subitem using the
> available C/M-[S]-<RET> commands. Just do M-<RET> <TAB>. And the same
> will work for inserting todo headings.
I'm not sure I follow the reasoning here: do you say that we don't
need to find a keybinding for `org-insert-subheading/subitem' because
it is already easy enough to insert a subheading/item using a certain
combinaison of commands?
Or do you suggest we need to find another prefix than "C-M-"? Which
one?
What matter the most to me here is the consistency of commands, but if
the keybindings can reflect that, all the better.
--
Bastien
next prev parent reply other threads:[~2023-12-25 9:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 9:04 Provide org-insert-subitem Dmitrii Korobeinikov
2020-02-02 7:49 ` Bastien
2020-02-02 10:11 ` Dmitrii Korobeinikov
2020-02-02 17:43 ` Adam Porter
2020-02-12 8:33 ` Bastien
2020-02-12 21:28 ` Adam Porter
2020-02-13 5:13 ` Corwin Brust
2020-02-13 8:04 ` Bastien
2020-02-13 18:45 ` Adam Porter
2020-02-14 10:02 ` Bastien
2023-12-08 2:51 ` Adam Porter
2023-12-09 14:09 ` Ihor Radchenko
2023-12-09 17:53 ` Bastien Guerry
2023-12-14 15:00 ` Ihor Radchenko
2023-12-25 9:14 ` Bastien [this message]
2023-12-25 9:40 ` Ihor Radchenko
2023-12-17 5:59 ` Adam Porter
2023-12-25 9:21 ` Bastien
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=87y1dive2x.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=adam@alphapapa.net \
--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).