From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] Inline tasks are exported, even with noexport tag
Date: Wed, 27 Feb 2013 22:01:35 +0100 [thread overview]
Message-ID: <86sj4h5v4g.fsf@somewhere.org> (raw)
In-Reply-To: 877gltstoc.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> The following ECM fails on 2 fronts:
>>
>> - the `noexport' tag on the inline task is not respected;
>
> Should it?
Well, it previously did. And that's pretty interesting: you can put "private"
inline blocks, and have them exported or not, depending of the target of your
document.
> Inlinetasks are not headlines, even though they use a somewhat similar
> syntax. :noexport: tag applies to trees. Inlinetasks do not define a tree.
For me, inline tasks were (up to now) exactly like trees but with an end, and
their contents was inline in the current entry, without disrupting the outline
structure.
We could use them to mirror "note" or "warning" blocks or paragraphs we find
in all books, and that in a portable manner (regarding the multi-backends).
As (I understood that) they were like headlines, we could anything like for
real headlines:
- adding tags
- adding TODO keywords
- adding drawers
- adding clocking information
- etc.
Is this not right anymore?
> More generally, `org-export-with-tasks', `org-export-select-tags' and
> `org-export-exclude-tags' only apply on headlines.
I understand there is a "yes for all" / "no for all" switch, but the ability
to mark some of the inline blocks NOT for export is a functionality which,
IMHO, we should avoid to drop.
> On the other hand, `org-export-with-inlinetasks' allows you to ignore
> inlinetasks completely during export. For conditional export, you may
> also want to look at drawers, which can be included/excluded by their
> name.
If inline tasks can or should be replaced by drawers, what is their use, then?
What remains as their fundamental reason of living?
I'd like that to be clarified for my own understanding.
>> - the exported contents (because of the previous item) is not compilable in
>> LaTeX (maybe the default in `org-latex-inlinetask' is not generic enough for
>> handling such a content, or there are restrictions on the contents of inline
>> tasks which I did not respect?)
>
> From the Org POV, you can put anything in an inlinetask excepted another
> inlinetask and a headline.
>
> `latex' backend puts contents within \fbox and a \minipage environments.
> It's possible that verbatim is not allowed within one of them, I didn't
> check. It's quite difficult to come up with something visually different
> and yet general enough. You can also use
> `org-latex-format-inlinetask-function'.
I'll give a look, thanks.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-02-27 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 14:15 [bug] Inline tasks are exported, even with noexport tag Sebastien Vauban
2013-02-27 14:44 ` Nicolas Goaziou
2013-02-27 21:01 ` Sebastien Vauban [this message]
2013-02-27 22:08 ` Nicolas Goaziou
2013-02-27 23:01 ` Bastien
2013-03-02 12:49 ` Nicolas Goaziou
2013-03-02 13:09 ` Bastien
2013-03-02 14:12 ` Nicolas Goaziou
2013-03-02 15:07 ` Bastien
2013-03-02 21:03 ` Sebastien Vauban
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=86sj4h5v4g.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).