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 21:58:16 +0100 [thread overview]
Message-ID: <86hallfbmf.fsf@somewhere.org> (raw)
In-Reply-To: 86fw15l2ze.fsf@iro.umontreal.ca
Hi François,
François Pinard wrote:
> 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.
>
> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>
>> Of course, I just push this change.
>> Done!
>
> Hi, all.
>
> Quickly seeing this exchange, and realizing I do not understand what
> "speed commands" are, I decided to search for the expression in the Org
> manual, and did not find it. (This is after a "git pull", done earlier
> today.) Should I seek the concept under some other name?
Yes, my bad; I should have said "speed keys". See the following:
;;** 15.3 (info "(org)Speed keys")
Well, you know that since 25 Sep 2012 22:31; I remember an exchange on that
with you: see http://comments.gmane.org/gmane.emacs.orgmode/60873.
> 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.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-02-09 20:58 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 [this message]
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=86hallfbmf.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).