Taking a look at your solution I realize where the bug lay as well. Level is unimportant, it just scanned too long previously (it should only look if the next headline contains "END", not look for the next headline with "END").

Anders Johansson

Den mån 17 feb 2014 23:05:02 skrev Nicolas Goaziou:

Anders Johansson <> writes:

I thought that I would be able to use both tasks with and without an
"END" line interchangeably:

*************** inlinetask without end
some text

*************** inlinetask with end
                         text inside inlinetask
*************** END

The problem (not so surprising really) is that the parser finds the
"END" of the second inlinetask and makes them nested in an export.

This should be fixed in maint. Thank you for reporting it.

For the record, inlinetasks cannot be nested, and the number of stars is
not meaningful, as long as it is greater than `org-inlinetask-min-level'.


Reply via email to