From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Custom keymaps on org blocks
Date: Mon, 05 Jun 2017 15:53:33 -0600 [thread overview]
Message-ID: <m2bmq2nlsy.fsf@andrew.cmu.edu> (raw)
Is there any interest in having custom keymaps on org blocks?
The idea I had is to have the option to make the major-mode keymaps be
active on the src blocks.
For example, you might want to use something like this to use the elpy
in ipython blocks and lispy-mode-map in emacs-lisp blocks
(defcustom org-src-block-keymaps
`(("ipython" . ,(let* ((map (copy-keymap elpy-mode-map)))
(define-key map (kbd "C-c C-c") 'org-ctrl-c-ctrl-c)
(define-key map (kbd "C-c '") 'org-edit-special)
map))
("emacs-lisp" . ,(let* ((map (copy-keymap lispy-mode-map)))
(define-key map (kbd "C-c C-c") 'org-ctrl-c-ctrl-c)
(define-key map (kbd "C-c '") 'org-edit-special)
map)))
"alist of custom keymaps for src blocks.")
The implementation is pretty simple, you just modify
org-fontify-meta-lines-and-blocks-1 with a line like this:
(when (assoc (org-no-properties lang) org-src-block-keymaps)
(add-text-properties
beg end `(local-map ,(cdr (assoc (org-no-properties lang)
org-src-block-keymaps)))))
I have tried this, and seems ok, and I wondered if anyone had an opinion
for or against this idea.
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next reply other threads:[~2017-06-06 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 21:53 John Kitchin [this message]
2017-06-06 18:16 ` Custom keymaps on org blocks Nicolas Goaziou
2017-06-07 12:58 ` John Kitchin
2017-06-07 13:21 ` Nicolas Goaziou
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=m2bmq2nlsy.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
/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).