all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Okamsn <okamsn@protonmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] `org-delete-char` and `org-delete-backward-char` don't respect `delete-active-region`
Date: Wed, 21 Jun 2023 10:14:27 +0000	[thread overview]
Message-ID: <87y1kdf7gc.fsf@localhost> (raw)
In-Reply-To: <e625df0a-0f9a-e986-4a9f-a9fac5533791@protonmail.com>

Okamsn <okamsn@protonmail.com> writes:

> `org-delete-char` and `org-delete-backward-char` don't respect
> `delete-active-region`

Clarification first.
`org-delete-char' and `org-delete-backward-char' are not supposed to
respect `delete-active-region'. They are the replacements for
`delete-char' and `delete-backward-char' that also do not respect it.
Org only re-binds `delete-char' and `delete-backward-char'.

> This works when `delete` is bound to `forward-delete-char` and 
> `backspace` is bound to `backward-delete-char-untabify`, because both 
> commands respect `delete-active-region`.
>
> This does not work with `org-delete-backward-char` or `org-delete-char`, 
> because those commands use `delete-char`, which does not respect 
> `delete-active-region`.

May you please explain what exactly you did? Or meow did? Did it bind
the Org functions inappropriately? Or are you asking to add new Org
commands that respect `delete-active-region'?

-- 
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>


  reply	other threads:[~2023-06-21 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18 18:31 [BUG] `org-delete-char` and `org-delete-backward-char` don't respect `delete-active-region` Okamsn
2023-06-21 10:14 ` Ihor Radchenko [this message]
2023-06-22  1:56   ` Okamsn
2023-07-19 12:44     ` Ihor Radchenko

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1kdf7gc.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=okamsn@protonmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.