From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Custom keymaps on org blocks
Date: Wed, 07 Jun 2017 15:21:53 +0200 [thread overview]
Message-ID: <87o9u0ylu6.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2mv9k0xau.fsf@andrew.cmu.edu> (John Kitchin's message of "Wed, 07 Jun 2017 06:58:17 -0600")
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> For once in a while uses this works, but this isn't really a solution
> for key-bindings that are composable, e.g. in lispy. There you can use
> single key-presses to navigate, rearrange, insert code, etc...
>
> Also it adds three chords to every key-binding out of the box, it would
> be fewer keys to just go to special edit mode unless you make a simpler
> key definition!
Sure, but I have the feeling that it isn't Org job to allow keybindings
for multiple major modes in the same buffer. Note that we already did
this with links, but I think that specific part of link revamp may have
gone too far.
Also, it could be troublesome because some interactive functions may
depend on a mode specific variables, which are not initialized while in
Org mode.
As far as Org is concerned, C-c ', i.e., `org-edit-special' is the way
to go, IMO.
WDYT?
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2017-06-07 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 21:53 Custom keymaps on org blocks John Kitchin
2017-06-06 18:16 ` Nicolas Goaziou
2017-06-07 12:58 ` John Kitchin
2017-06-07 13:21 ` Nicolas Goaziou [this message]
2017-06-07 13:50 ` John Kitchin
2017-06-08 0:22 ` Grant Rettke
2017-06-10 9:03 ` Nicolas Goaziou
2017-06-10 13:58 ` John Kitchin
2017-06-10 19:31 ` John Kitchin
2018-09-05 15:52 ` Matt Price
2017-06-07 1:22 ` Grant Rettke
2017-06-07 12:49 ` John Kitchin
2017-06-07 23:52 ` Grant Rettke
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=87o9u0ylu6.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).