From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <rudolf@adamkovic.org>
Cc: Dan Drake <dan.drake@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-cut-subtree should respect org-ctrl-k-protect-subtree
Date: Sun, 22 Sep 2024 16:35:17 +0000 [thread overview]
Message-ID: <87wmj3pry2.fsf@localhost> (raw)
In-Reply-To: <m2r0a0gwqk.fsf@adamkovic.org>
Rudolf Adamkovič <rudolf@adamkovic.org> writes:
>> May you list the editing commands that you think can benefit from an
>> extra confirmation dialog?
>
> Me? I regularly archive subtrees by mistake. :)
You can re-bind C-c C-x C-a to
`org-archive-subtree-default-with-confirmation' then.
>> ... which are `org-ctrl-k-protect-subtree', `org-ctrl-c-ctrl-c-hook',
>> and `org-ctrl-c-ctrl-c-final-hook'. What do you want to do with the
>> latter two?
>
> The original idea was: If we are renaming the function, we might
> consider looking at the entire family, as naming after key strokes is
> not idiomatic in Emacs, nor a good idea, and should be slowly fixed
> long-term, IMO. If we are not renaming anything, the idea can be
> ignored, of course.
Yes, we do want to rename all these to something more readable in the
long term. But that's separate from merging the commands or variables
together.
--
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>
prev parent reply other threads:[~2024-09-22 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 13:10 org-cut-subtree should respect org-ctrl-k-protect-subtree Dan Drake
2024-08-27 14:15 ` Rudolf Adamkovič
2024-08-28 11:46 ` Dan Drake
2024-08-29 10:39 ` Rudolf Adamkovič
2024-09-01 16:20 ` Ihor Radchenko
2024-09-01 18:49 ` Dan Drake
2024-09-15 12:46 ` Ihor Radchenko
2024-09-17 23:36 ` Dan Drake
2024-10-20 12:46 ` Ihor Radchenko
2024-09-03 23:09 ` Rudolf Adamkovič
2024-09-22 16:35 ` Ihor Radchenko [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=87wmj3pry2.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dan.drake@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rudolf@adamkovic.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).