emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why not enable extra keys by default?
Date: Thu, 11 Jan 2024 12:42:39 +0000	[thread overview]
Message-ID: <87jzogjb28.fsf@localhost> (raw)
In-Reply-To: <m27ckgzwka.fsf@me.com>

Rudolf Adamkovič <salutis@me.com> writes:

> I have the 'org-use-extra-keys' customization enabled to avoid reaching
> for the arrow keys, but the variable needs to be set before loading Org,
> which makes literate configuration a bit more complex.

> Other Emacs commands have alternative keys bound by default, which makes
> me wonder, why does Org need the 'org-use-extra-keys' customization?  If
> the user rebinds any of the extra keys, their personal key bindings take
> precedence, so all should work well for everyone, right?
>
> If so, then why not (1) enable the extra keys by default and (2)
> deprecate the 'org-use-extra-keys' customization?

A comment in org-keys.el says:

;;  We only set them when really needed because otherwise the
;;  menus don't show the simple keys

Also, it is not true that re-binding will always work - if user binds
keys before Org mode is loaded (for example, globally), Org mode will
overwrite them.

Finally, C-c <left> / <right> conflict with winner-mode.
ESC <left> / <right> are bound to forward/backward-word by default.

-- 
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:[~2024-01-11 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 21:51 Why not enable extra keys by default? Rudolf Adamkovič
2024-01-11 12:42 ` Ihor Radchenko [this message]
2024-01-12 17:06   ` 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=87jzogjb28.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=salutis@me.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).