From: John Hendy <jw.hendy@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Error with :wrap org in babel and 8.0-pre
Date: Mon, 15 Apr 2013 16:29:31 -0500 [thread overview]
Message-ID: <CA+M2ft8+45+-c6cm2GMJs+8x3UQxM1ziBvXceD4HuLPYSoZi9w@mail.gmail.com> (raw)
In-Reply-To: <86bo9fldp1.fsf@somewhere.org>
On Mon, Apr 15, 2013 at 3:51 PM, Sebastien Vauban
<wxhgmqzgwmuf@spammotel.com> wrote:
> Eric Schulte wrote:
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>> John Hendy <jw.hendy@gmail.com> writes:
>>>> On Mon, Apr 15, 2013 at 2:56 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>>>>> John Hendy <jw.hendy@gmail.com> writes:
>>>>>
>>>>>> #+RESULTS:
>>>>>> #+BEGIN_org
>>>>>> ...
>>>>>> #+END_org
>>>>>
>>>>> This is wrong. We discussed it months ago on this ML and, IIRC, Babel
>>>>> should produce "#+begin_src org" blocks, not "#+begin_org". Org
>>>>> documentation specifies it too.
>>>>
>>>> "Wrong," as in =:wrap org= behavior is currently a bug? Or "wrong" in that
>>>> for my given use case, I shouldn't be using =:wrap org=?
>>>
>>> Wrong as is "the current behaviour is a bug". It is expected to produce
>>> "#+begin_src org" blocks. Its use case is to generate dead data:
>>
>> I disagree, the current behavior is *not* a bug. From the manual.
>>
>> ,----
>> | 14.8.2.23 ':wrap'
>> | .................
>> |
>> | The ':wrap' header argument is used to mark the results of source block
>> | evaluation. The header argument can be passed a string that will be
>> | appended to '#+BEGIN_' and '#+END_', which will then be used to wrap the
>> | results. If not string is specified then the results will be wrapped in
>> | a '#+BEGIN/END_RESULTS' block.
>> `----
>>
>> I think you're confusing ":results org" with ":wrap org".
>
> And it's even possible to use ":wrap SRC org" to get the same as ":results
> org"...
True, however I don't get the same output as I used to with this and
think it's essentially useless now. =#+begin_src org/end_src= used to
give me the equivalent of essentially a block of Org-mode syntax that
would be interpreted and parsed just as if it had no #+begin/end
around it. Now, it's output to LaTeX in \begin{verbatim} /
\end{verbatim}. It's treated like source code, not Org-mode text to be
exported.
=#+begin_src org= seems to be no different than =#+begin_example= or
=#+begin_src lang :exports code :eval no=
John
>
>> That said, I don't think there is ever a case when you would want to use
>> ":wrap org". The solution to the original question is to use ":results
>> drawer".
>
> Best regards,
> Seb
>
> --
> Sebastien Vauban
>
>
next prev parent reply other threads:[~2013-04-15 21:29 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 [this message]
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
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=CA+M2ft8+45+-c6cm2GMJs+8x3UQxM1ziBvXceD4HuLPYSoZi9w@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).