From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Suggestion/bug: Parse inlinetask "END" with level sensitivity
Date: Mon, 17 Feb 2014 23:05:02 +0100
Message-ID: <87eh31o0oh.fsf@gmail.com>
References: <53024A87.6030901@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48409)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1WFWJ1-0004c1-1s
	for emacs-orgmode@gnu.org; Mon, 17 Feb 2014 17:04:59 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1WFWIs-0007xK-GS
	for emacs-orgmode@gnu.org; Mon, 17 Feb 2014 17:04:50 -0500
Received: from mail-wi0-x232.google.com ([2a00:1450:400c:c05::232]:62877)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1WFWIs-0007x9-9A
	for emacs-orgmode@gnu.org; Mon, 17 Feb 2014 17:04:42 -0500
Received: by mail-wi0-f178.google.com with SMTP id cc10so2865735wib.17
	for <emacs-orgmode@gnu.org>; Mon, 17 Feb 2014 14:04:41 -0800 (PST)
In-Reply-To: <53024A87.6030901@gmail.com> (Anders Johansson's message of "Mon,
	17 Feb 2014 18:44:39 +0100")
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: Anders Johansson <mejlaandersj@gmail.com>
Cc: emacs-orgmode@gnu.org

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 is
not meaningful, as long as it is greater than `org-inlinetask-min-level'.


Regards,

-- 
Nicolas Goaziou