Re: [O] [new exporter] two unexpected behaviours of an #+INCLUDEd #+call

2012-10-28 Thread Nicolas Goaziou
Hello, Myles English mylesengl...@gmail.com writes: Given the situation below, I would expect that the block named xxx would never be evaluated: #- file b.org --- #+TITLE: b.org #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport * A

Re: [O] [new exporter] two unexpected behaviours of an #+INCLUDEd #+call

2012-10-22 Thread Myles English
Myles English writes: Hi, I think there is a bug here. Just adding some evidence: similar behaviour was reported in this thread: http://lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg00634.html Myles Given the situation below, I would expect that the block named xxx would never

Re: [O] [new exporter] two unexpected behaviours of an #+INCLUDEd #+call

2012-10-22 Thread Nicolas Goaziou
Hello, Myles English mylesengl...@gmail.com writes: Just adding some evidence: similar behaviour was reported in this thread: http://lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg00634.html Yes, I'm working on it on my spare time but it requires some modifications to Babel core, so

[O] [new exporter] two unexpected behaviours of an #+INCLUDEd #+call

2012-10-18 Thread Myles English
Hi, I think there is a bug here. Given the situation below, I would expect that the block named xxx would never be evaluated: #- file b.org --- #+TITLE: b.org #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport * A heading