Re: [RFC] [PATCH] Introduce org-specific functions for (next/previous)-visible-heading

[Andreas Leha <andreas.leha@med.uni-goettingen.de>]

Hi,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Aaron Ecay <aaronecay@gmail.com> 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
>> incorrect.
>
> 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
of *'s.

>
>> 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.

Regards,
Andreas