From: Grant Rettke <gcr@wisdomandwonder.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Custom keymaps on org blocks
Date: Wed, 7 Jun 2017 18:52:36 -0500 [thread overview]
Message-ID: <CAAjq1mcDo9KHRhC1urdnfwsFAkejG-0deOMBRcrzxPjAEAXZSA@mail.gmail.com> (raw)
In-Reply-To: <m2o9u00xpt.fsf@andrew.cmu.edu>
On Wed, Jun 7, 2017 at 7:49 AM, John Kitchin <jkitchin@andrew.cmu.edu> wrote:
> Grant Rettke writes:
>
>> You want Polymode: https://github.com/vspinu/polymode
>
> I have never been able to get polymode to work. Do have an incantation
> that works?
I forgot that I set it up for R markdown files. But it did work on my
machine after manually installing the `polymode' package.
https://github.com/grettke/home/blob/master/.emacs.el#L1992-L2005
>> It is confusing alternating between the Org major a mode and the
>> source block major mode as you scroll through documents. One second
>> you are an author for humans and the other an author for the computer.
>> That is how literate programming is defined in theory, but in practice
>> I don't do it like that because it is mentally jarring.
>
> Interesting perspective. I find switching to special edit mode jarring,
> particularly when it is just for the key bindings, e.g. lispy mode, or
> getting python indentation to work.
We are both surprised!
prev parent reply other threads:[~2017-06-07 23:52 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
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 [this message]
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=CAAjq1mcDo9KHRhC1urdnfwsFAkejG-0deOMBRcrzxPjAEAXZSA@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--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).