From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ista Zahn Subject: Re: Source block processing changes Date: Tue, 6 Nov 2012 12:45:11 -0500 Message-ID: References: <87pq3qlvbt.fsf@gmail.com> <87ehk68ywe.fsf@gmail.com> <87txt27itx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:37863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TVnDX-0002IF-2r for emacs-orgmode@gnu.org; Tue, 06 Nov 2012 12:45:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TVnDQ-00081n-1n for emacs-orgmode@gnu.org; Tue, 06 Nov 2012 12:45:38 -0500 Received: from mail-vc0-f169.google.com ([209.85.220.169]:38515) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TVnDP-00081g-TV for emacs-orgmode@gnu.org; Tue, 06 Nov 2012 12:45:31 -0500 Received: by mail-vc0-f169.google.com with SMTP id fl17so776885vcb.0 for ; Tue, 06 Nov 2012 09:45:31 -0800 (PST) In-Reply-To: <87txt27itx.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode Mailinglist , Eric Schulte On Tue, Nov 6, 2012 at 12:16 PM, Nicolas Goaziou wrote: > Ista Zahn writes: > >> On Tue, Nov 6, 2012 at 11:44 AM, Nicolas Goaziou wrote: >>> Ista Zahn 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,