From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [bug] org-inlinetask produces invalid xhtml Date: Thu, 11 Aug 2011 14:17:29 +0200 Message-ID: <87wrekjg6e.fsf@gmail.com> References: <81ipq7j1xp.fsf@gmail.com> <81aabjj17d.fsf@gmail.com> <87wrenn4ic.fsf@gmail.com> <81vcu7i1g6.fsf@gmail.com> <874o1qn756.fsf@gmail.com> <81y5z2p82h.fsf@gmail.com> <871uwsl01h.fsf@gmail.com> <814o1ochl8.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:45255) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrUD5-00083M-PX for emacs-orgmode@gnu.org; Thu, 11 Aug 2011 08:18:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QrUD0-0005NJ-P8 for emacs-orgmode@gnu.org; Thu, 11 Aug 2011 08:18:03 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:64105) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrUD0-0005NF-It for emacs-orgmode@gnu.org; Thu, 11 Aug 2011 08:17:58 -0400 Received: by wyi11 with SMTP id 11so1631211wyi.0 for ; Thu, 11 Aug 2011 05:17:57 -0700 (PDT) In-Reply-To: <814o1ochl8.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 11 Aug 2011 16:51:19 +0530") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Jambunathan K Cc: emacs-orgmode@gnu.org Jambunathan K writes: >> As far as I can tell, inline tasks are not designed to be nested. > > May be C-c C-x t should throw an error and enforce this. Done. > If inlinetasks cannot be nested, may I know how one would use > org-inlinetask-promote and org-inlinetask-demote. > > I understand that it's presence implies that even though inlinetasks > cannot be nested they could occur at various levels Indeed. > implying that inline task deeper than a certain level are treated > differently than others. I fear that exporters are not aware about this implication. The templates may support a `relative-level' keyword. An inline task at `org-inlinetask-min-level' would set it at 0 and so on. > Does Org provide a way to NOT export trees deeper than a certain > level? I don't think so, though you can remove them via a hook just before export. Regards, -- Nicolas Goaziou