Eric Schulte wrote: > Nicolas Goaziou <n.goaz...@gmail.com> writes: >> John Hendy <jw.he...@gmail.com> writes: >>> On Mon, Apr 15, 2013 at 2:56 PM, Nicolas Goaziou <n.goaz...@gmail.com> >>> wrote: >>>> John Hendy <jw.he...@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"... > 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
