emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Error with :wrap org in babel and 8.0-pre
Date: Tue, 16 Apr 2013 10:23:57 +0200	[thread overview]
Message-ID: <m2bo9eanoi.fsf@christianmoe.com> (raw)
In-Reply-To: <87obdfe5mo.fsf@gmail.com>


Eric Schulte writes:
>> - Is =:results drawer= what we want as the syntax to get org syntax
>> parsed by the exporter?
>
> Yes.
>
>> Just guessing from the name, it strikes me as a fix or enhancement for
>> some other behavior/option that's now being applied to code as an
>> after thought.
>>
>
> As I recall this solution came about because drawers are the best (maybe
> only) way to demarcate a region without changing its semantics (which is
> exactly what we want in this case).

I suppose you've considered delimiting results in general with e.g. a
line like #+END_RESULTS?

Needless clutter for the most part, I know. But perhaps useful in this
kind of case. Also safe, semantically neutral, and possibly more
intuitive than drawers, with less special behaviors in terms of
visibility and export.

Yours,
Christian

  parent reply	other threads:[~2013-04-16  8:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 22:45 Error with :wrap org in babel and 8.0-pre John Hendy
2013-04-12 22:24 ` Eric Schulte
2013-04-15 17:59   ` John Hendy
2013-04-15 18:12     ` Eric Schulte
2013-04-15 19:35       ` John Hendy
2013-04-15 19:48         ` Andreas Leha
2013-04-15 19:52           ` John Hendy
2013-04-15 19:56         ` Eric Schulte
2013-04-15 19:56         ` Nicolas Goaziou
2013-04-15 20:05           ` John Hendy
2013-04-15 20:15             ` Nicolas Goaziou
2013-04-15 20:28               ` Eric Schulte
2013-04-15 20:51                 ` Sebastien Vauban
2013-04-15 21:29                   ` John Hendy
2013-04-15 21:44                     ` Sebastien Vauban
2013-04-15 21:51                       ` John Hendy
2013-04-15 21:24                 ` John Hendy
2013-04-15 21:42                   ` Sebastien Vauban
2013-04-15 22:38                   ` Eric Schulte
2013-04-15 22:48                     ` John Hendy
2013-04-15 23:27                       ` Eric Schulte
2013-04-15 23:56                         ` Thomas S. Dye
2013-04-16  2:37                           ` Eric Schulte
2013-04-16  7:58                         ` Sebastien Vauban
2013-04-16  8:23                         ` Christian Moe [this message]
2013-04-16 14:58                           ` John Hendy
2013-04-16 15:24                             ` Eric Schulte
2013-04-16 21:06                             ` Christian Moe
2013-04-15 20:09           ` Sebastien Vauban
2013-04-15 20:22             ` Nicolas Goaziou
2013-04-15 19:47       ` Sebastien Vauban
2013-04-15 21:38         ` John Hendy

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=m2bo9eanoi.fsf@christianmoe.com \
    --to=mail@christianmoe.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).