From: "Eric Schulte" <schulte.eric@gmail.com>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] key binding requests
Date: Sun, 11 Jul 2010 21:53:36 -0700 [thread overview]
Message-ID: <8739vpmh9c.fsf@gmail.com> (raw)
In-Reply-To: m07hl3pgbg.fsf@gmail.com
Hi Austin,
Austin Frank <austin.frank@gmail.com> writes:
> Hello!
>
> I'm loving the level of polish and sophistication that have been
> achieved with org-babel. My entire PhD thesis is currently written in
> org and org-babel, and it's the best authoring system I've ever used.
>
Fantastic! happy to hear your finding it useful
>
> That said, I have a couple of features that I regularly find myself
> missing. I wonder whether other folks might also find them useful.
>
> First, in terms of navigation, I would love to have keybindings under
> the C-c C-v prefix that would navigate to the next and previous babel
> blocks. org-babel-goto-named-source-block[fn:1] is great, but a) not all my
> blocks are named, and b) I don't always remember the name of the block
> I'm looking for. On that note...
>
Done, C-c C-v n and C-c C-v p now navigate to the next and previous code
blocks respectively. C-c C-v p used to be used for viewing the expanded
body of a code block, this functionality is now behind C-c C-v v for
"view"
>
> Currently, org-babel-goto-named-source-block doesn't currently offer
> any completion facilities in my setup. Is there a way to hook it into
> the rest of org's completion mechanisms so that I can hit tab to
> complete the names of my source blocks?
>
Done, C-c C-v g for "goto code block" now has completing read. There is
also now C-c C-v r for "goto result" which also has completing reads
>
> Finally, to go along with facilities to navigate from source block to
> source block, I'd also make regular use of something like
> org-execute-src-block-and-step, which would execute the current block
> and then jump to the next (or previous) one.
>
There are already C-c C-v b and C-c C-v s for evaluating the current
buffer, or the current subtree respectively. Also, with the new "goto
next code block" functionality it should be easy to implement the
behavior you describe in a short macro.
>
> Thanks again for these excellent tools,
> /au
>
> Footnotes:
>
> [fn:1] This is the only function that uses "source" instead of "src" in
> its name. Should this be changed for consistency?
Thanks for pointing this out, I've made this change as well.
Thanks for all the great suggestions! -- Eric
prev parent reply other threads:[~2010-07-12 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 14:22 [babel] key binding requests Austin Frank
2010-07-10 17:17 ` Jonathan Arkell
2010-07-12 4:53 ` Eric Schulte
2010-07-12 4:53 ` Eric Schulte [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=8739vpmh9c.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=austin.frank@gmail.com \
--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).