Re: [O] [bug] Inline tasks are exported, even with noexport tag
Hello, Bastien b...@altern.org writes: From on intuitive point of view: Inline tasks support tags, and :noexport: means Don't export me, me being whatever is tagged. So I support Sébastien's idea here: :noexport: should remove inline tasks from the exported string. Maybe we need to set the `org-export-filter-inlinetask-functions' at some point to support this? Then should it also support `org-export-with-tasks' variable? It's hard to tell what should be supported and what shouldn't. Regards, -- Nicolas Goaziou
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: So I support Sébastien's idea here: :noexport: should remove inline tasks from the exported string. Maybe we need to set the `org-export-filter-inlinetask-functions' at some point to support this? Then should it also support `org-export-with-tasks' variable? Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline tasks with a TODO keyword should be exported. -- Bastien
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Bastien b...@gnu.org writes: Then should it also support `org-export-with-tasks' variable? Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline tasks with a TODO keyword should be exported. Done. Regards, -- Nicolas Goaziou
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@gnu.org writes: Then should it also support `org-export-with-tasks' variable? Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline tasks with a TODO keyword should be exported. Done. Thanks! -- Bastien
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Bastien wrote: Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@gnu.org writes: Then should it also support `org-export-with-tasks' variable? Yes. E.g. if `org-export-with-tasks' is set 'todo, only inline tasks with a TODO keyword should be exported. Done. Thanks! Thanks! Best regards, Seb -- Sebastien Vauban
[O] [bug] Inline tasks are exported, even with noexport tag
Hello,
The following ECM fails on 2 fronts:
- the `noexport' tag on the inline task is not respected;
- 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?)
Best regards,
Seb
--8---cut here---start-8---
#+TITLE: ECM Noexport not respected, and failure to export
#+AUTHOR:Seb Vauban
#+Time-stamp: 2013-02-27 Wed 15:07
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t ^:{}
* Private headline :noexport:
You don't see this. Good!
* Public headline
Normal body text...
*** This error report should be private :noexport:
When pushing Submit, I got the error:
#+begin_example
[ServletException in:/WEB-INF/sharedfiles/pdef/split/action_n235.jsp] No
getter method available for property submitinfo.xor_n249_n250 for bean under
name ViewCaseForm'
#+end_example
Maybe due to UTF-8 in the file =C:\WebClient\src\SubmitInfo.java=.
See as well
[[file:WebClient/src/tools/pdef/makefile][file:WebClient/src/tools/pdef/makefile]].
*** END
Follow-up to normal body text...
--8---cut here---end---8---
--
Sebastien Vauban
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Hello, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: The following ECM fails on 2 fronts: - the `noexport' tag on the inline task is not respected; Should it? Inlinetasks are not headlines, even though they use a somewhat similar syntax. :noexport: tag applies to trees. Inlinetasks do not define a tree. More generally, `org-export-with-tasks', `org-export-select-tags' and `org-export-exclude-tags' only apply on headlines. 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. - 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'. Regards, -- Nicolas Goaziou
Re: [O] [bug] Inline tasks are exported, even with noexport tag
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
Re: [O] [bug] Inline tasks are exported, even with noexport tag
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Should it? Inlinetasks are not headlines, even though they use a somewhat similar syntax. :noexport: tag applies to trees. Inlinetasks do not define a tree. From on intuitive point of view: Inline tasks support tags, and :noexport: means Don't export me, me being whatever is tagged. So I support Sébastien's idea here: :noexport: should remove inline tasks from the exported string. Maybe we need to set the `org-export-filter-inlinetask-functions' at some point to support this? Thanks, -- Bastien
