From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Error with :wrap org in babel and 8.0-pre Date: Mon, 15 Apr 2013 16:29:31 -0500 Message-ID: References: <87li8ncqzq.fsf@gmail.com> <87li8jfysj.fsf@gmail.com> <87y5cjy3du.fsf@gmail.com> <87txn7y2hb.fsf@gmail.com> <874nf7fsix.fsf@gmail.com> <86bo9fldp1.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URqxz-00014B-1M for emacs-orgmode@gnu.org; Mon, 15 Apr 2013 17:29:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URqxx-0001yj-OX for emacs-orgmode@gnu.org; Mon, 15 Apr 2013 17:29:34 -0400 Received: from mail-lb0-f169.google.com ([209.85.217.169]:41702) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URqxx-0001ya-7Q for emacs-orgmode@gnu.org; Mon, 15 Apr 2013 17:29:33 -0400 Received: by mail-lb0-f169.google.com with SMTP id p11so4980535lbi.28 for ; Mon, 15 Apr 2013 14:29:31 -0700 (PDT) In-Reply-To: <86bo9fldp1.fsf@somewhere.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: emacs-orgmode On Mon, Apr 15, 2013 at 3:51 PM, Sebastien Vauban wrote: > Eric Schulte wrote: >> Nicolas Goaziou writes: >>> John Hendy writes: >>>> On Mon, Apr 15, 2013 at 2:56 PM, Nicolas Goaziou wrote: >>>>> John Hendy 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 > >