From: ggggJambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BABEL] Speed keys
Date: Sun, 05 Sep 2010 01:43:34 +0530 [thread overview]
Message-ID: <81pqwt1d3l.fsf@gmail.com> (raw)
In-Reply-To: <8762yleei5.fsf@gmail.com> (Eric Schulte's message of "Sat, 04 Sep 2010 07:14:55 -0600")
>> Is it possible Speed Keys (Refer Org Manual - Sec. 15.3) for
>> Babel blocks?
>>
Eric> Hi Jambunathan, That sounds like a good idea. I suppose
Eric> initially the speed keys should just mirror the babel key map?
Exactly.
As long as the cursor is on a #+begin_src (and/or #+end_src), one need
not bother about typing C-c C-v. So a keypress 'n' would do what C-c C-v
n would do.
More importantly emerging new sequences like, C-c C-v C-x TAB could be
composed as
1. Push a mark (C-SPC) [Optional]
2. Move to babel guard line using user preferred method [See my other
post on the list]
3. C-x TAB
One of the problems with C-c C-v prefix is that I tend to forget it if I
revisit Babel say after a week's time. (Not nitpicking here!). The
reason is that I simply couldn't contrive a convenient menemonic that
would make me recollect C-v. So jumping to the babel guard line and
issuing the needed command is a good fall back option.
Jambunathan K.
next prev parent reply other threads:[~2010-09-04 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 12:39 [BABEL] Speed keys Jambunathan K
2010-09-04 13:14 ` Eric Schulte
2010-09-04 20:11 ` Jambunathan K
2010-09-04 20:13 ` ggggJambunathan K [this message]
2010-09-04 21:48 ` Carsten Dominik
2010-09-05 10:03 ` Jambunathan K
2010-09-06 22:57 ` Jambunathan K
2010-09-21 12:36 ` Carsten Dominik
2010-09-21 13:05 ` Eric Schulte
2010-09-23 19:51 ` Eric Schulte
2010-09-26 14:21 ` FSF Copyright Assignment Jambunathan K
2010-09-26 20:02 ` Eric Schulte
2010-10-01 13:31 ` Sébastien Vauban
2010-10-01 15:10 ` Eric Schulte
2010-10-01 15:41 ` Sébastien Vauban
2010-10-06 11:44 ` Dan Davison
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=81pqwt1d3l.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).