From: mithraeum <mithraeum@protonmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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:47:16 +0000 [thread overview]
Message-ID: <QQNxxn5HtAeICGPk7nwp4C9hebpi6-DHouCeMCDTM1VpLCxOZUksMwpPE_ZJkOYDvWBhL8BEp6Drsfkxzfon3h-slE9UQ3vVlCB2iNPOfQo=@protonmail.com> (raw)
In-Reply-To: <87d0qrvtg9.fsf@nicolasgoaziou.fr>
On Tuesday, November 27, 2018 12:02 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> 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.
I thought org-agenda was part of org. It's org-agenda which I've been going through recently to bind in to hydras, so that's why I used it as an example. I hope the principle of separating functions from bindings applies to the rest of org as well, though.
> 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.
I can understand how hydra not being shipped with Emacs would preclude it from being used by Org. Maybe it could inspire the way Org handles menuing, however. As opinionated as it might be, it's very flexible and powerful, and its keybindings and menus are clearly separated from the functions they invoke.
But if there is something even better and cleaner than hydra, I'd be all for it.
next prev parent reply other threads:[~2018-11-27 9:47 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
2018-11-27 9:47 ` mithraeum [this message]
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='QQNxxn5HtAeICGPk7nwp4C9hebpi6-DHouCeMCDTM1VpLCxOZUksMwpPE_ZJkOYDvWBhL8BEp6Drsfkxzfon3h-slE9UQ3vVlCB2iNPOfQo=@protonmail.com' \
--to=mithraeum@protonmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).