From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anders Johansson <mejlaandersj@gmail.com>
Subject: Re: Suggestion/bug: Parse inlinetask "END" with level sensitivity
Date: Tue, 18 Feb 2014 00:22:38 +0100
Message-ID: <530299BE.2070604@gmail.com>
References: <53024A87.6030901@gmail.com> <87eh31o0oh.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39029)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mejlaandersj@gmail.com>) id 1WFXWS-0003Nq-My
	for emacs-orgmode@gnu.org; Mon, 17 Feb 2014 18:22:55 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mejlaandersj@gmail.com>) id 1WFXWL-0007sn-7n
	for emacs-orgmode@gnu.org; Mon, 17 Feb 2014 18:22:48 -0500
Received: from velox.its.uu.se ([130.238.7.74]:39258)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mejlaandersj@gmail.com>) id 1WFXWL-0007sX-0q
	for emacs-orgmode@gnu.org; Mon, 17 Feb 2014 18:22:41 -0500
In-Reply-To: <87eh31o0oh.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org

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

Regards,
Anders Johansson

Den m=C3=A5n 17 feb 2014 23:05:02 skrev Nicolas Goaziou:
> Hello,
>
> Anders Johansson <mejlaandersj@gmail.com> 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 i=
s
> not meaningful, as long as it is greater than `org-inlinetask-min-level=
'.
>
>
> Regards,
>