From: John Hendy <jw.hendy@gmail.com>
To: Christian Moe <mail@christianmoe.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>,
Eric Schulte <schulte.eric@gmail.com>
Subject: Re: Error with :wrap org in babel and 8.0-pre
Date: Tue, 16 Apr 2013 09:58:51 -0500 [thread overview]
Message-ID: <CA+M2ft8iaLNW8Ojx1yPKVkzs34-T8EJZL-=ZBXWdybit5NNqTg@mail.gmail.com> (raw)
In-Reply-To: <m2bo9eanoi.fsf@christianmoe.com>
On Tue, Apr 16, 2013 at 3:23 AM, Christian Moe <mail@christianmoe.com> wrote:
>
> 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?
>
As in compiling with simply =:results output raw= and then adding my
own #+end_results line after the block?
If so, I haven't tried that. But :wrap with no second argument creates
#+begin/end_results, which doesn't export correctly.
Thanks,
John
> 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
>
>
next prev parent reply other threads:[~2013-04-16 15:11 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 ` 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
2013-04-16 14:58 ` John Hendy [this message]
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:56 ` Eric Schulte
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='CA+M2ft8iaLNW8Ojx1yPKVkzs34-T8EJZL-=ZBXWdybit5NNqTg@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--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).