emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ista Zahn <istazahn@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>,
	Eric Schulte <schulte.eric@gmail.com>
Subject: Re: Source block processing changes
Date: Tue, 6 Nov 2012 12:45:11 -0500	[thread overview]
Message-ID: <CA+vqiLF3PgyDroFo+qX4ooSmnFaVSfTcOz9G1=qpp4qrJkbZxA@mail.gmail.com> (raw)
In-Reply-To: <87txt27itx.fsf@gmail.com>

On Tue, Nov 6, 2012 at 12:16 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Ista Zahn <istazahn@gmail.com> writes:
>
>> On Tue, Nov 6, 2012 at 11:44 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>>> Ista Zahn <istazahn@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,

  reply	other threads:[~2012-11-06 17:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 16:56 Source block processing changes Ista Zahn
2012-11-05 17:25 ` Nicolas Goaziou
2012-11-05 18:45   ` Ista Zahn
2012-11-06  9:59     ` Sebastien Vauban
2012-11-06 10:00       ` Nicolas Goaziou
2012-11-06 18:53       ` Achim Gratz
2012-11-06 13:22 ` Eric Schulte
2012-11-06 14:51   ` Ista Zahn
2012-11-06 16:44     ` Nicolas Goaziou
2012-11-06 17:06       ` Ista Zahn
2012-11-06 17:16         ` Nicolas Goaziou
2012-11-06 17:45           ` Ista Zahn [this message]
2012-11-06 17:48   ` Ista Zahn
2012-11-06 18:30     ` Ista Zahn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+vqiLF3PgyDroFo+qX4ooSmnFaVSfTcOz9G1=qpp4qrJkbZxA@mail.gmail.com' \
    --to=istazahn@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=schulte.eric@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).