From: Giacomo M <jackjackk@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Get to next NEXT headline with one key
Date: Fri, 7 Mar 2014 13:44:37 +0100 [thread overview]
Message-ID: <CA+GKSr4kQ6hVuiDuJm-eGGN_bMHofN5+jW5o1Mohk1We1p-OjQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ51EToUe+JZyTqX9RMqJ_LcNeW+a6TjZdb8EDisUmErmp1R6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Sorry for having been ambiguous, I meant the next headline with a "NEXT"
todo keyword.
Thanks
Il 07/mar/2014 13:37 "John Kitchin" <jkitchin@andrew.cmu.edu> ha scritto:
> I do not understand what you are asking for. in my emacs/org pressing n
> does go to the next headline. (at least after running (setq
> org-use-speed-commands t)) and being at the beginning of a headline.
>
>
> John
>
> -----------------------------------
> John Kitchin
> Associate Professor
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> http://kitchingroup.cheme.cmu.edu
>
>
>
> 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?
>>
>> Thanks,
>>
>> Giacomo
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2065 bytes --]
next prev parent reply other threads:[~2014-03-07 12:44 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 [this message]
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
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=CA+GKSr4kQ6hVuiDuJm-eGGN_bMHofN5+jW5o1Mohk1We1p-OjQ@mail.gmail.com \
--to=jackjackk@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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 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).