From: Andreas Leha <email@example.com>
Subject: Re: [RFC] [PATCH] Introduce org-specific functions for (next/previous)-visible-heading
Date: Mon, 19 Jan 2015 21:45:04 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Nicolas Goaziou <email@example.com> writes:
> Aaron Ecay <firstname.lastname@example.org> writes:
>> By default, org uses outline-next-visible-heading and the -previous-
>> variant for the C-c C-n and C-c C-p keys, which means these commands
>> stop on inline tasks (since they don’t know to skip them). This seems
> Are you sure? This is a way to move to the next inline task (which is
> some kind of headline). How do you move to it otherwise?
I agree with Aaron. Actually I have written a message about that exact
topic (without a patch, though) already last year -- but that did not
get through, as it seems.
I use inline-tasks extensively (and map them to todonotes in the pdf
export). And I am always surprised to end up at an inline-task when I
navigate the document.
If I need to find the next inline task I can always search for a lot
>> The attached patch adds inlinetask-aware org functions for these keys.
>> Comments are welcome.
> You don't need to implement anything new, actually. If you need to
> ignore inlinetasks for something, just wrap it within
> `org-with-limited-levels' macro:
> (org-with-limited-levels (outline-next-visible-heading))
That wrapper is handy and works like a charm. Thanks.
But I'd still argue that the default behaviour should be to skip inline
tasks for all navigation commands in org.
next prev parent reply other threads:[~2015-01-19 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 5:14 [RFC] [PATCH] Introduce org-specific functions for (next/previous)-visible-heading Aaron Ecay
2015-01-19 17:58 ` Nicolas Goaziou
2015-01-19 21:45 ` Andreas Leha [this message]
2015-01-19 21:56 ` Rasmus
2015-01-20 12:00 ` Nicolas Goaziou
2015-01-20 23:56 ` Aaron Ecay
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).