From: Oleh Krehel <ohwoeowho@gmail.com>
To: Leo Ufimtsev <lufimtse@redhat.com>
Cc: emacs-orgmode@gnu.org, Zhihao Ding <zhihao.ding@imm.ox.ac.uk>
Subject: Re: navigate between source code blocks
Date: Fri, 01 May 2015 17:13:28 +0200 [thread overview]
Message-ID: <87pp6kjppj.fsf@gmail.com> (raw)
In-Reply-To: <1786587997.8149765.1430488523520.JavaMail.zimbra@redhat.com> (Leo Ufimtsev's message of "Fri, 1 May 2015 09:55:23 -0400 (EDT)")
Leo Ufimtsev <lufimtse@redhat.com> writes:
>>And it's got the best Helm implementation for navigating to
> headings.
>
> Well, when I hear someone use the word 'best', I see it as a challenge X-D.
>
> I used worf-goto for a while. It's certainly amazing and on the odd occasion I still use it, but lately I've switched over to: helm-org-in-buffer-headings
>
> The difference is that worf-goto only looks at the specific headings (e.g the line it self), where as helm-org-in-buffer-headings searches the whole hierarchy.
>
> E.g if I have a structure like this:
>
> * Gdb
> ** Break
> *** on line (1)
> *** on function
> * Eclipse
> ** Break
> *** on line
> *** on function
>
> And I search for "gdb break line", then I will not get a match with worf-goto, but helm-org-in-buffer-headings does do a match on (1).
>
> For example in the attached screenshot I search for "gdb cmd break". It's also smart enough to trim long headings.
>
> This is particularly useful for finding the deeply nested sub-items.
>
> from what I gather, worf doesn't have an equivalent:
> https://github.com/abo-abo/worf/blob/master/worf.el
> Imho it would benefit from having something of that sort in the
> package.
Thanks for the feedback, Leo. It's doable, but then it would be pretty
much identical to helm-org-in-buffer-headings. If you or anyone else is
interested, post at https://github.com/abo-abo/worf/issues.
>> It just takes vi-style "hjkl" arrows, because
> Emacs-style "bnpf" arrows aren't convenient.
>
> Well, I use the Colemak layout, so hjkl is actually not very
> convenient for me :-/. Meh.
Well, it's always something, isn't it :)
By the way, I'm trying to go with general-purpose tools these days.
Here's a link to the search that you mentioned using swiper:
http://oremacs.com/download/org-mode-swiper.png.
Swiper is an isearch replacement, so I could just:
1. "C-s" break -> see 38 matches.
2. "C-a" \* "SPC" -> see 9 matches.
3. "C-n" repeatedly to navigate to the one that I want.
As you see, I kind of stole your notes and the org-bullets
customization, so thanks for that:)
Oleh
next prev parent reply other threads:[~2015-05-01 15:19 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
2015-05-01 13:55 ` Leo Ufimtsev
2015-05-01 15:13 ` Oleh Krehel [this message]
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=87pp6kjppj.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lufimtse@redhat.com \
--cc=zhihao.ding@imm.ox.ac.uk \
/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).