From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] org-inlinetask produces invalid xhtml
Date: Thu, 11 Aug 2011 14:17:29 +0200 [thread overview]
Message-ID: <87wrekjg6e.fsf@gmail.com> (raw)
In-Reply-To: <814o1ochl8.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 11 Aug 2011 16:51:19 +0530")
Jambunathan K <kjambunathan@gmail.com> 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
next prev parent reply other threads:[~2011-08-11 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 16:36 [bug] org-inlinetask produces invalid xhtml Jambunathan K
2011-08-08 16:51 ` Jambunathan K
2011-08-08 18:26 ` Nicolas Goaziou
2011-08-09 5:44 ` Jambunathan K
2011-08-09 11:42 ` Nicolas Goaziou
2011-08-09 21:51 ` Jambunathan K
2011-08-09 23:47 ` suvayu ali
2011-08-11 10:23 ` Nicolas Goaziou
2011-08-11 11:21 ` Jambunathan K
2011-08-11 12:17 ` Nicolas Goaziou [this message]
2011-08-11 11:21 ` Jambunathan K
2011-08-11 20:38 ` Jambunathan K
2011-08-16 19:30 ` Bastien
2011-08-16 19:21 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrekjg6e.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).