On 26.9.2013, at 13:26, Nicolas Goaziou wrote: > Hello, > > François Pinard writes: > >> Nicolas Goaziou writes: >> >>> François Pinard writes: >> >>>> The spirit behind :export: is [...] >> >>> I agree, this is a misfeature. This should be fixed in master. Thank >>> you for bringing it out. >> >> Thanks as well. :-) > > OTOH, this "fix" introduces another problem. > > What if a user wants to both use :export: tag and export text before > first headline? An almost equivalent solution for him would be to add > a headline before that text and append it an :export: tag. But in that > case, he will get the additional headline in the output, which isn't > desirable. IOW, it is easier to make that text disappear than to make it > appear. > > IOW, even though the new behaviour is more logical, in the end, I'm not > sure it is desirable. It's the old "good" versus "best" story. The new behavior is the correct one. :export: selects stuff to be exported. A way to have initial text and some trees would be to add :noexport: to the ones that should not be exported. If there is string desire to be able to export initial text with :export: tags, the only solutions I see would be an additional variable with an #+OPTIONS equivalent, like org-export-force-initial-content. Default obviously off, setting the variable to t with list or customize not recommended, but possible to set it on a per file basis with #+OPTIONS - Carsten > > WDYT? > > > Regards, > > -- > Nicolas Goaziou >