From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: navigating between non-code blocks?
Date: Sat, 09 Feb 2013 22:15:07 +0100 [thread overview]
Message-ID: <86d2w9ur38.fsf@somewhere.org> (raw)
In-Reply-To: 86hallfbmf.fsf@somewhere.org
Hi François,
"Sebastien Vauban" wrote:
> François Pinard wrote:
>> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>>> Bill White <billw-BUE4RdJlFM5BDgjK7y7TUQ@public.gmane.org> writes:
>>
>>> C-c C-F (`org-next-block')
>>> C-c C-B (`org-previous-block')
>>>
>>>> And, echoing Sebastien, `F' and `B' as speed commands would be very
>>>> handy.
>>>
>>> Of course, I just push this change.
>>> Done!
>>
>> Within Emacs, `C-c C-f' is bound to org-next-block, while the manual, in
>> the Motion node, says that `C-c C-f' is bound to org-forward-same-level. As
>> for `C-c C-F' (really `C-c C-S-f'), it does not seem to be bound and fall
>> back on `C-c C-f'.
>
> I'll test, and report.
Indeed...
╭──── C-h k C-c C-S-f
│
│ C-c C-f (translated from C-c C-S-f) runs the command org-next-block, which is
│ an interactive Lisp function in `org.el'.
│
│ It is bound to C-c C-f.
│
│ (org-next-block ARG &optional BACKWARD BLOCK-REGEXP)
│
│ Jump to the next block.
╰────
and
╭──── C-h k C-c C-f
│
│ C-c C-f runs the command org-next-block, which is an interactive Lisp function
│ in `org.el'.
│
│ It is bound to C-c C-f.
│
│ (org-next-block ARG &optional BACKWARD BLOCK-REGEXP)
│
│ Jump to the next block.
╰────
So, C-c C-F does work on code blocks, but for a bad reason (C-c C-f, instead).
And, don't know why, but the speed key `F' is not working for me, on a freshly
pulled Org:
Org-mode version 7.9.3e (7.9.3e-965-g16118a @ d:/Users/fni/Public/Repositories/org-mode/lisp/)
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-02-09 21:15 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
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 [this message]
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=86d2w9ur38.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).