From: Dan Davison <davison@stats.ox.ac.uk>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Richard Riley <rileyrg@gmail.com>
Subject: Re: org-babel - utility to ease chopping src chunks into smaller org entries
Date: Mon, 20 Sep 2010 21:09:36 +0100 [thread overview]
Message-ID: <87iq20p473.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: 87fwx4sco2.fsf@gmail.com
[...]
>>> I was just pulling up my email to share my next iteration when I saw
>>> your next iteration. They look very similar. If my version covers all
>>> of your use cases, then I'd like to add it to the Babel key map,
>>> probably under "d" for demarcate or delimit, unless you can think of a
>>> better mnemonic.
>
> I've just added this to the org-mode repo.
>
>> Not in the babel key map - in the org key map (I use it most in normal
>> non src org entries to mark a block of elisp as src for samples/examples).
>
> For now it still lives in the babel keymap behind (C-c C-v d) since it
> is fundamentally code-block related,
For me, "fundamentally code-block related", in the absence of
execution-related functionality, points to org-src.el rather than
org-babel, so I suggest naming this function
org-src-demarcate-block. The babel keymap is still a good place for a
binding -- I think it's reasonable for the babel keymap to accomodate
pure code block stuff in addition to execution/tangling stuff.
Dan
next prev parent reply other threads:[~2010-09-20 20:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 1:48 org-babel - utility to ease chopping src chunks into smaller org entries Richard Riley
2010-09-19 18:21 ` Eric Schulte
2010-09-19 22:03 ` Richard Riley
2010-09-19 23:20 ` Richard Riley
2010-09-20 3:41 ` Eric Schulte
2010-09-20 5:18 ` Richard Riley
2010-09-20 14:30 ` Eric Schulte
2010-09-20 15:15 ` Sébastien Vauban
2010-09-20 22:21 ` Sébastien Vauban
2010-09-21 12:46 ` Eric Schulte
2010-09-21 13:49 ` Dan Davison
2010-09-21 14:37 ` Sébastien Vauban
2010-09-21 12:44 ` Eric Schulte
2010-09-21 15:19 ` Sébastien Vauban
2010-09-20 20:09 ` Dan Davison [this message]
2010-09-21 7:58 ` Christian Moe
2010-09-21 11:17 ` Richard Riley
2010-09-21 13:04 ` Eric Schulte
2010-09-21 14:35 ` Christian Moe
2010-09-21 14:50 ` Dan Davison
2010-09-21 15:35 ` Eric Schulte
2010-09-24 13:24 ` Requests about the code demarcation Sébastien Vauban
2010-09-27 13:18 ` Eric Schulte
2010-09-27 13:47 ` Sébastien Vauban
2010-09-27 14:36 ` Sébastien Vauban
2010-09-27 14:58 ` Eric Schulte
2010-09-30 18:17 ` Achim Gratz
2010-09-30 22:19 ` Eric Schulte
2010-10-01 19:28 ` Achim Gratz
2010-10-17 11:53 ` Richard Riley
2010-09-21 6:33 ` org-babel - utility to ease chopping src chunks into smaller org entries Achim Gratz
2010-09-21 13:01 ` Eric Schulte
2010-09-21 17:03 ` Achim Gratz
2010-09-19 21:24 ` Sébastien Vauban
2010-09-19 21:44 ` Richard Riley
2010-09-19 21:52 ` Sébastien Vauban
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=87iq20p473.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=rileyrg@gmail.com \
--cc=schulte.eric@gmail.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).