From: "Eric Schulte" <schulte.eric@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BABEL] Commands for navigation
Date: Wed, 08 Sep 2010 00:24:38 -0600 [thread overview]
Message-ID: <877hiw21n0.fsf@gmail.com> (raw)
In-Reply-To: 81zkvx1wz0.fsf@gmail.com
Hi,
Jambunathan K <kjambunathan@gmail.com> writes:
> I think the navigation commands should wrap around to beginning or end
> of file as necessary possibly after throwing an error. The error
> messages down below need to be replaced with more user-friendly
> messages. When I see anything such big or as cryptic I get apprehensive
> that something is broken badly.
>
I've updated these two function so that they will now throw more
informative error messages.
>
> Is there a quick way to place the cursor at the beginning or end of
> the babel block? I could think of two options -
>
> 1. Augment C-c C-v p and C-c C-v n to jump to the beg/end of the current
> block
>
> 2. Overload C-c C-u (within org-mode) to also mean jump to the enclosing
> structural block.
>
> Given a choice I would lean towards (2).
>
I would lean towards (2) as well, however I can also see the value of
maintaining the behavior of C-c C-u /regardless/ of the local context.
As a temporary (and maybe sufficient to be a permanent) solution I've
bound C-c C-v u to `org-babel-goto-src-block-head'.
>
> ps: Quick navigation to babel guard lines could be useful in
> conjunction with speed keys (when supported)
>
Makes sense, and the above command could easily be rebound in a personal
configuration to an easier key-sequence than the default provided.
Cheers -- Eric
prev parent reply other threads:[~2010-09-08 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 13:04 [BABEL] Commands for navigation Jambunathan K
2010-09-08 6:24 ` 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=877hiw21n0.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).