On Tue, Nov 6, 2012 at 12:16 PM, Nicolas Goaziou <n.goaz...@gmail.com> wrote: > Ista Zahn <istaz...@gmail.com> writes: > >> On Tue, Nov 6, 2012 at 11:44 AM, Nicolas Goaziou <n.goaz...@gmail.com> wrote: >>> Ista Zahn <istaz...@gmail.com> writes: >>> >>>> Thank you, all is working as desired now! One small niggle: the >>>> '::RESULTS:' and ':END:' strings are included in the exported html. >>>> Not sure if this is intentional, but it seems to me that they should >>>> be removed (or at lease given a class so we can hide them via css) >>> >>> That's because you're inserting a headline within a drawer, which isn't >>> valid Org syntax. You cannot use a drawer for your specific use-case. >> >> Well, it works at the moment (I can live with the extra ':RESULTS:' >> strings). So currently I _can_ use a drawer for my use case -- the >> question is whether this is likely to break in the future. > > This is already broken. In Org syntax, > > :RESULTS: > * Headline > :END: > > means a paragraph containing ":RESULTS:" text, then an headline > containing a section with a paragraph containing ":END:" text. In other > words, headlines have precedence over drawers. > > Expecting Org to recognize a drawer here is like playing with fire. You > cannot know when it will burn you. > >> Another question is what is and is not allowed in a drawer? Is this >> documented? > > A drawer can contain anything but a headline and another drawer.
OK, great. The ability to generate headlines from source blocks is not crucial, I'll change them to plain lists. I'm not > talking about properties drawer which is special. This is not explicitly > documented. > > > Regards,
