emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Zhihao Ding <zhihao.ding@imm.ox.ac.uk>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: Leo Ufimtsev <lufimtse@redhat.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: navigate between source code blocks
Date: Fri, 1 May 2015 08:36:08 +0000	[thread overview]
Message-ID: <f81542fb-3b95-46e5-bc9f-4cadaa69034d@HUB06.ad.oak.ox.ac.uk> (raw)
In-Reply-To: <87a8xpo7dy.fsf@gmail.com>

Thank guys. Wolf is new to me and I am trying it now, it already feels 
very attractive! This increases my navigation efficiency quite a bit!  

Zhihao


> On 30 Apr 2015, at 18:25, Oleh Krehel <ohwoeowho@gmail.com> wrote:
> 
> Leo Ufimtsev <lufimtse@redhat.com> writes:
> 
>> Worf I think is a bit on the vi side of things. Helm is more generic.
> 
> Worf is as much on the vi side of things, as `org-use-speed-commands'
> are. Almost not at all. It just takes vi-style "hjkl" arrows, because
> Emacs-style "bnpf" arrows aren't convenient.
> 
> And it's got the best Helm implementation for navigating to
> headings. I've just added named blocks to this list as well.
> Screenshot: http://oremacs.com/download/worf-goto.png.
> The command to call is "M-x" `worf-goto' or "g" while in `worf-mode'.
> 
> Oleh

  reply	other threads:[~2015-05-01  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 14:47 navigate between source code blocks Zhihao Ding
2015-04-28  7:22 ` Oleh Krehel
2015-04-29  8:20   ` Zhihao Ding
2015-04-30 16:48     ` Leo Ufimtsev
2015-04-30 17:25       ` Oleh Krehel
2015-05-01  8:36         ` Zhihao Ding [this message]
2015-05-01 13:55         ` Leo Ufimtsev
2015-05-01 15:13           ` Oleh Krehel
2015-05-04 14:00             ` Leo Ufimtsev
2015-05-04 10:08       ` Sebastien Vauban
2015-05-04 14:04         ` Leo Ufimtsev

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=f81542fb-3b95-46e5-bc9f-4cadaa69034d@HUB06.ad.oak.ox.ac.uk \
    --to=zhihao.ding@imm.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=lufimtse@redhat.com \
    --cc=ohwoeowho@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).