emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: mithraeum <mithraeum@protonmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Feature request - Decouple org's keybindings from their functions
Date: Tue, 27 Nov 2018 09:02:46 +0100	[thread overview]
Message-ID: <87d0qrvtg9.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <zgdfQsfGgD_jIOJWbAcXO-OUFv_XRlNgR_NfdCNrnVrMg2kNqD_vjhecTHb8H1sZxIj55yPzHdHGtxGcemm73mvhshQOZhPIT2xx7vGZheY=@protonmail.com> (mithraeum's message of "Tue, 27 Nov 2018 02:50:49 +0000")

Hello,

mithraeum <mithraeum@protonmail.com> writes:

> I'd like to request that org's keybindings be separated from the functions they use to do their work.
>
> This would greatly ease the use of these functions by people who want to use their own keybindings rather than relying on keybindings that org provides.
>
> The reason I ask is that recently I've been going through
> org-agenda.el

Are you talking about Org a whole, or just Org agenda? All your examples
are about the latter. If it's about Org agenda, well, I'm afraid to say
there are so many things to fix there that keybindings are only the tip
of the iceberg.

> Ultimately, I think it would be much, much cleaner for org to use
> a dedicated, well designed menuing package like hydra to do its
> menuing.

Hydra is very opinionated about what a menu is. It may not be a good
default. Also, it doesn't ship with Emacs. So Org cannot rely on it from
the start.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2018-11-27  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  2:50 Feature request - Decouple org's keybindings from their functions mithraeum
2018-11-27  8:02 ` Nicolas Goaziou [this message]
2018-11-27  9:47   ` mithraeum
2018-11-28  8:04     ` stardiviner
2018-11-28  9:11       ` 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=87d0qrvtg9.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mithraeum@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 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).