Hello,
Rasmus ras...@gmx.us writes:
[...]
To *me*, inlinetasks have got nothing to do with headlines (the syntax is
unfortunate, especially for people who write Org without org-mode).
Indeed. It makes sense.
Thus, I like Aaron patch, though we could add a defcustom if it breaks
Hello,
2015ko urtarrilak 20an, Nicolas Goaziou-ek idatzi zuen:
[...]
Then the patch is fine (with `org-with-limited-levels' instead of
re-inventing the wheel).
Thanks everyone for the feedback. The patch is pushed (with an entry in
ORG-NEWS).
--
Aaron Ecay
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Aaron Ecay aarone...@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
Hi,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
But I'd still argue that the default behaviour should be to skip inline
tasks for all navigation commands in org.
I use inlinetasks in a similar way to Andreas: i.e. as TODO-notes in my
ongoing work.
To *me*, inlinetasks have got
Hello,
Aaron Ecay aarone...@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
Hello,
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.
The attached patch adds inlinetask-aware org functions for these
