emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Rudolf Adamkovič" <rudolf@adamkovic.org>
To: Dan Drake <dan.drake@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-cut-subtree should respect org-ctrl-k-protect-subtree
Date: Thu, 29 Aug 2024 12:39:59 +0200	[thread overview]
Message-ID: <m2a5gvehog.fsf@adamkovic.org> (raw)
In-Reply-To: <CAKqbAeEYY1ymE6UyyrR_RMh1SmQHb4RSrAGQ2rF1WoMmXdZgUw@mail.gmail.com>

Dan Drake <dan.drake@gmail.com> writes:

> What do you think we should have for the new name for
> org-ctrl-k-protect-subtree? Just "org-protect-subtree"?

I like that name, but perhaps we should zoom out a bit and look at the
entire family of the non-idiomatic `org-ctrl-*' variables.

Most importantly, though, we should wait for Ihor to say his thoughts,
as he is THE expert to consult, especially with regards to the APIs and
overall design of the Org mode.

> How do we handle renaming the variable? We'd want some way of
> deprecating the old one and so on.

Fortunately, Emacs has us covered.  See `defalias'.  Such functions are
used all over the Emacs code base, allowing it to move forward, for
decades to come, in a backward compatible way.

Thank you for making Org better!

Rudy
-- 
"The whole science is nothing more than a refinement of everyday
thinking."  --- Albert Einstein, 1879-1955

Rudolf Adamkovič <rudolf@adamkovic.org> [he/him]
http://adamkovic.org


  reply	other threads:[~2024-08-29 10:40 UTC|newest]

Thread overview: 9+ 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č [this message]
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-09-03 23:09   ` Rudolf Adamkovič

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=m2a5gvehog.fsf@adamkovic.org \
    --to=rudolf@adamkovic.org \
    --cc=dan.drake@gmail.com \
    --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).