From: Giacomo M <jackjackk@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Get to next NEXT headline with one key
Date: Fri, 07 Mar 2014 17:23:12 +0100 [thread overview]
Message-ID: <5319F270.10605@gmail.com> (raw)
In-Reply-To: <CAA01p3phM7P6UfKg9KRyJu_E-7N4ufKqzf4BMxMgySu-nHzb3w@mail.gmail.com>
(typo in my previous email: s/to Matt/to John/)
Il 07/03/2014 15:44, Oleh ha scritto:
> If you're feeling adventurous, you can try my new minor mode:
> https://github.com/abo-abo/worf.
Thank you, Oleh!
Just tried it, and I think it has several convenient features.
> And commands work from start of #+... as well.
Like this one.
> Here's how I've implemented the functionality that you want:
>
> "j"/"k" are bound move down/up just like in vim, but they move by
> headings or #+ markers.
> But "K" can change their behavior temporarily: it will prompt you for
> a char that corresponds to a keyword:
> t - TODO
> d - DONE
> n - NEXT
> c - CANCELLED
>
> After a keyword is set, "j"/"k" will move by this keyword instead,
> until any command other than "j"/"k" is issued (for instance "m",
> which reveals heading). After that "j"/"k" will return to their
> regular behavior.
>
Question: is there a particular reason for restricting keyword j/k
movement only to
- headlines at lower/equal levels (I get stuck in the subtree with the
first NEXT)?
- visible headlines (I miss folded NEXT entries)?
Still eventually I would like to pack those "Knjm" keys into just one
key to replicate what is done by Matt my-org-next-next() function.
> And if you're trying out the mode, make sure to try "g" and "h" - those
> are my two favorites. `helm` and `ace-jump-mode` respectively are required
> in order for these commands to work. I'm planning to add the package to MELPA,
> so the dependencies would be downloaded automatically, but I don't want to add
> it until I've assigned all the alphanumeric keys:)
I didn't know ace-jump-base... it really made my day! And yes, g and h
can be quite useful.
Do you think that the selection procedure of *helm* could be compatible
with sth like ace-jump-line-mode? The problem then will be to find a
good keyword also for activating the ace commands.
I think this is a good step towards the ultimate keystroke-minimizing
editing environment... it's just a thousand key-bindings-to-memorize
away, but I can see it!
next prev parent reply other threads:[~2014-03-07 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 12:13 Get to next NEXT headline with one key Giacomo M
2014-03-07 12:37 ` John Kitchin
2014-03-07 12:44 ` Giacomo M
2014-03-07 13:54 ` Matt Lundin
2014-03-07 14:28 ` Giacomo M
2014-03-07 14:44 ` Oleh
2014-03-07 16:23 ` Giacomo M [this message]
2014-03-09 12:39 ` Oleh
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=5319F270.10605@gmail.com \
--to=jackjackk@gmail.com \
--cc=emacs-orgmode@gnu.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).