emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bill White <billw@wolfram.com>
To: emacs-orgmode@gnu.org
Subject: Re: navigating between non-code blocks?
Date: Fri, 08 Feb 2013 13:25:24 -0600	[thread overview]
Message-ID: <877gmiy5ej.fsf@wolfram.com> (raw)
In-Reply-To: 87sj56rcsj.fsf@bzg.ath.cx

On Fri Feb 08 2013 at 10:11, Bastien <bzg@altern.org> wrote:

> Hi Bill,
>
> Bill White <billw@wolfram.com> writes:
>
>> I sometimes have a lot of these in an org file and it would be handy
>> to navigate among them easily.  It seems that block navigation is set
>> up to work only with *code* blocks.
>
> You now have 
>
> C-c C-F (`org-next-block') 
> C-c C-B (`org-previous-block')
>
> for navigating blocks.
>
> Thanks for the suggestion!

And thanks for implementing it.  One small code problem, though - I
think BLOCK-REGEXP should default to org-block-regexp.  Otherwise,
block-regexp isn't defined and the function just goes to the next
org-babel-src-block-regexp

(Sorry, I don't recall offhand how to set that up in elisp.)

And, echoing Sebastien, `F' and `B' as speed commands would be very
handy.

Thanks!

bw
-- 
Bill White . billw@wolfram.com
"No ma'am, we're musicians."

  parent reply	other threads:[~2013-02-08 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 20:50 navigating between non-code blocks? Bill White
2013-02-08 16:11 ` Bastien
2013-02-08 16:47   ` Sebastien Vauban
2013-02-08 18:39     ` Bastien
2013-02-08 19:25   ` Bill White [this message]
2013-02-09  9:25     ` Bastien
2013-02-09 19:08     ` François Pinard
2013-02-09 20:58       ` Sebastien Vauban
2013-02-09 21:15         ` Sebastien Vauban
2013-02-11 13:21           ` Bastien
2013-02-09 23:58         ` François Pinard
2013-02-10  7:37           ` Sebastien 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=877gmiy5ej.fsf@wolfram.com \
    --to=billw@wolfram.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).