From: Ihor Radchenko <yantar92@posteo.net>
To: Bastien <bzg@gnu.org>
Cc: Adam Porter <adam@alphapapa.net>, emacs-orgmode@gnu.org
Subject: Re: Provide org-insert-subitem
Date: Mon, 25 Dec 2023 09:40:31 +0000 [thread overview]
Message-ID: <875y0m1uy8.fsf@localhost> (raw)
In-Reply-To: <87y1dive2x.fsf@gnu.org>
Bastien <bzg@gnu.org> writes:
>> 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?
I mean that it seems to be easy to insert subheading/subitem already.
You can try:
* Heading<point>
M-RET TAB
or
* Heading<point>
C-S-RET TAB
or
- item<point>
M-RET TAB
We even have this documented in the Structural Editing section of the
manual:
‘<TAB>’ (‘org-cycle’)
In a new entry with no text yet, the first ‘<TAB>’ demotes the
entry to become a child of the previous one. The next ‘<TAB>’
makes it a parent, and so on, all the way to top level. Yet
another ‘<TAB>’, and you are back to the initial level.
Probably, we should mention "subitem/subheading" words in the index or
find some other way to emphasize that it is possible to demote
subheading with TAB.
> What matter the most to me here is the consistency of commands, but if
> the keybindings can reflect that, all the better.
For me, it is important to keep consistency of the keys as well - these
are the core Org keys, and they should be as intuitive as possible.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-12-25 9:38 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
2023-12-25 9:40 ` Ihor Radchenko [this message]
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=875y0m1uy8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).