From: Carsten Dominik <carsten.dominik@gmail.com>
To: Daniel Clemente <n142857@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [babel] new key bindings
Date: Mon, 17 May 2010 11:05:36 +0200 [thread overview]
Message-ID: <0BD52615-F10B-4847-ACD8-75FD6010D8E6@gmail.com> (raw)
In-Reply-To: <AANLkTikDY8RvjzAAcTomD8rBgp1Dvw_cwSQ3OxPn37aY@mail.gmail.com>
On May 17, 2010, at 9:27 AM, Daniel Clemente wrote:
> I think this key reminder table should be somehow displayed or
> offered under a C-c C-v prefix, in the same way as C-c a, C-c C-a, C-
> c e.
> Or at least under C-c C-v ? or C-c C-v h
>
> -- Daniel
>
> On Thu, May 13, 2010 at 7:57 AM, Eric Schulte
> <schulte.eric@gmail.com> wrote:
> Org-babel is now making use of the newly available C-c C-v key
> binding.
>
> All Org-babel keybindings are now located behind this prefix, see the
> updated org reference card (/doc/orgcard.pdf in the org-mode repo) for
> the specific keybindings, they are also shown below.
>
> Best -- Eric
>
>
> execute code block at point
> C-c C-c
> open results of code block at point
> C-c C-o
> preview body of code block at point
> C-c C-v C-p
> go to named code block
> C-c C-v C-g
> execute all code blocks in current buffer
> C-c C-v C-b
> execute all code blocks in current subtree
> C-c C-v C-s
> tangle code blocks in current file
> C-c C-v C-t
> tangle code blocks in supplied file
> C-c C-v C-T
> ingest all code blocks in supplied file into the Library of Babel
> C-c C-v C-l
> switch to the session of the current code block
> C-c C-v C-z
> view sha1 hash of the current code block
> C-c C-v C-h
Indeed, eric, you should not bind C-h in this keymap - this
is one of those conventions. If you don't, then C-v C-v C-h
will display the keys in this prefix map automatically.
- Carsten
next prev parent reply other threads:[~2010-05-17 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 5:57 [babel] new key bindings Eric Schulte
2010-05-17 7:27 ` Daniel Clemente
2010-05-17 9:05 ` Carsten Dominik [this message]
2010-05-17 23:09 ` Eric Schulte
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=0BD52615-F10B-4847-ACD8-75FD6010D8E6@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@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).