From: Matt Lundin <mdl@imapmail.org>
To: Giacomo M <jackjackk@gmail.com>
Cc: emacs-orgmode@gnu.org, John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Get to next NEXT headline with one key
Date: Fri, 07 Mar 2014 07:54:04 -0600 [thread overview]
Message-ID: <87k3c6glmr.fsf@fastmail.fm> (raw)
In-Reply-To: <CA+GKSr4kQ6hVuiDuJm-eGGN_bMHofN5+jW5o1Mohk1We1p-OjQ@mail.gmail.com> (Giacomo M.'s message of "Fri, 7 Mar 2014 13:44:37 +0100")
> On Fri, Mar 7, 2014 at 7:13 AM, Giacomo M <jackjackk@gmail.com>
> wrote:
>
> Dear all,
> I would like, by pressing the speed command N, to be brought to
> the next NEXT headline. I can see that somehow the functions
> involved could be org-match-sparse-tree and next-error, but I
> don't know how to code a programmatic execution of the two
> (unfortunately I don't speak elisp very well) into a function
> that can then be specified in the org-speed-commands-user
> customization.
>
> Is there anybody so kind to guide me to the (probably trivial)
> solution?
>
Giacomo M <jackjackk@gmail.com> writes:
> Sorry for having been ambiguous, I meant the next headline with a
> "NEXT" todo keyword.
> Thanks
Here's a very quick hack/proof of concept. There's very likely a better
way to do it. This is simply to illustrate the general idea.
--8<---------------cut here---------------start------------->8---
(defun my-org-next-next ()
(interactive)
(forward-word)
(when (re-search-forward "\\*+\\s-+NEXT" nil t)
(org-reveal t))
(org-back-to-heading))
(add-to-list 'org-speed-commands-user '("N" . (org-speed-move-safe 'my-org-next-next)))
--8<---------------cut here---------------end--------------->8---
Best,
Matt
next prev parent reply other threads:[~2014-03-07 13:54 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 [this message]
2014-03-07 14:28 ` Giacomo M
2014-03-07 14:44 ` Oleh
2014-03-07 16:23 ` Giacomo M
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3c6glmr.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=jackjackk@gmail.com \
--cc=jkitchin@andrew.cmu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.