From: Ihor Radchenko <yantar92@posteo.net>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH 0/4] Structure editing when region is active
Date: Sun, 05 Feb 2023 11:11:32 +0000 [thread overview]
Message-ID: <87cz6oe597.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8v41_cENLxWXew=H9ONuTPR_damTemTmT5-MAm34_f_ng@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> thanks for the patches. out of curiosity, does e.g. m-up m-up up deactivate?
No. The patches make M-<up>/<down>/<left>/<right> not deactivate.
Nothing else is affected.
If there are use-cases when these commands should deactivate, please share
them.
--
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-02-05 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:31 [PATCH 0/4] Structure editing when region is active Ihor Radchenko
2023-01-15 12:31 ` [PATCH 1/4] Preserve active region after structure edits Ihor Radchenko
2023-01-15 12:31 ` [PATCH 2/4] Preserve active region when toggling heading state Ihor Radchenko
2023-01-15 12:31 ` [PATCH 3/4] org-metaup, org-metadown: Move subtrees in active region Ihor Radchenko
2023-01-15 12:31 ` [PATCH 4/4] org-manual.org: Document changes in 8f6fcd709, 5719a8163, and eda9909a9 Ihor Radchenko
2023-01-16 0:24 ` [PATCH 0/4] Structure editing when region is active Samuel Wales
2023-01-16 11:17 ` Ihor Radchenko
2023-01-17 1:45 ` Samuel Wales
2023-01-17 9:46 ` Ihor Radchenko
2023-01-18 1:11 ` Samuel Wales
2023-01-18 10:14 ` Ihor Radchenko
2023-02-04 22:45 ` Samuel Wales
2023-02-05 11:11 ` Ihor Radchenko [this message]
2023-02-04 13:54 ` Ihor Radchenko
2023-02-06 21:00 ` Rudolf Adamkovič
2023-02-07 10:56 ` Ihor Radchenko
2023-02-15 18:36 ` Rudolf Adamkovič
2023-02-15 20:35 ` Ihor Radchenko
2023-02-18 21:18 ` Philipp Kiefer
2023-04-02 14:19 ` 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
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=87cz6oe597.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.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 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).