From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giuseppe Lipari Subject: Re: what happened to :wrap HTML ? Date: Thu, 25 Feb 2016 08:32:54 +0000 Message-ID: References: <87r3g17rpu.fsf@alphaville.usersys.redhat.com> <87mvqp4tdw.fsf@nicolasgoaziou.fr> <87ziup67li.fsf@gmx.us> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c05aff6fffd02052c940723 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYrMF-0005NR-Hj for emacs-orgmode@gnu.org; Thu, 25 Feb 2016 03:33:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYrM9-0003Lk-NE for emacs-orgmode@gnu.org; Thu, 25 Feb 2016 03:33:11 -0500 Received: from mail-wm0-x229.google.com ([2a00:1450:400c:c09::229]:37784) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYrM9-0003LU-C8 for emacs-orgmode@gnu.org; Thu, 25 Feb 2016 03:33:05 -0500 Received: by mail-wm0-x229.google.com with SMTP id g62so16781514wme.0 for ; Thu, 25 Feb 2016 00:33:05 -0800 (PST) In-Reply-To: <87ziup67li.fsf@gmx.us> 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: Rasmus , emacs-orgmode@gnu.org --94eb2c05aff6fffd02052c940723 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, :wrap export HTML is perfectly fine for me, and it opens more possibilities, so I am willing to upgrade my org files to the new syntax (they are not so many). Thank you for the fast response, Giuseppe Lipari Le mer. 24 f=C3=A9vr. 2016 =C3=A0 23:56, Rasmus a =C3=A9cri= t : > Nicolas Goaziou writes: > > > Hello, > > > > Nick Dokos writes: > > > >> Giuseppe Lipari writes: > >> > >>> Hello, > >>> > >>> I used to generate html code with a python script using org-babel, > like this: > >>> > >>> %------- example.org ---------% > >>> * This is an example of export in HTML > >>> #+BEGIN_SRC python :exports results :results output :wrap HTML > >>> print "
  • first item
    • " > >>> print "
  • second item
    • " > >>> print "
" > >>> #+END_SRC > >>> %------- example.org ---------% > >>> > >>> This used to work just fine and produce a nice unordered list in > >>> html. Until the moment I updated to the > >>> current development version: > >>> > >>> Org-mode version 8.3.4 (release_8.3.4-588-g924431 @ > /home/lipari/elisp/org-mode/lisp/) > >>> > >>> Now, it produces the attached screenshot: > >>> > >>> snapshot > >>> > >>> Hence my question: what happened to ":wrap HTML" ?? Is there an > equivalent way to express the same > >>> behaviour as before? > >>> > >> > >> I bet :wrap HTMP produces > >> > >> #+BEGIN_HTML > >> ... > >> #+END_HTML > >> > >> instead of > >> > >> #+BEGIN_EXPORT HTML > >> #+END_EXPORT > > > > So I guess the OP should write :wrap export HTML. > > > > We could also add the export part automatically, but that would limit > > the value of the parameter (e.g., impossible to do anything else than > > export blocks) > > We need to allow special blocks. But the question is whether we can > "guess" when something is a backend and do the right thing. It=E2=80=99s= probably > a "can of worms" to try to guess. > > Rasmus > > -- > Nothing's wrong with an email that ends in a minor key > > > --94eb2c05aff6fffd02052c940723 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

:wrap export HTML is pe= rfectly fine for me, and it opens more possibilities, so I am willing to up= grade my org files to the new syntax (they are not so many).

= Thank you for the fast response,

Giuseppe Lipari

=
Le=C2=A0mer. 24 f=C3=A9vr. 2016= =C3=A0=C2=A023:56, Rasmus <rasmus@gmx.= us> a =C3=A9crit=C2=A0:
Nico= las Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Nick Dokos <n= dokos@gmail.com> writes:
>
>> Giuseppe Lipari <giulipari@gmail.com> writes:
>>
>>> Hello,
>>>
>>> I used to generate html code with a python script using org-ba= bel, like this:
>>>
>>> %------- example.org ---------%
>>> * This is an example of export in HTML
>>> #+BEGIN_SRC python :exports results :results output :wrap HTML=
>>> print "<ul> <li> first item</li>"<= br> >>> print "<li> second item </li>"
>>> print "</ul>"
>>> #+END_SRC
>>> %------- example.org ---------%
>>>
>>> This used to work just fine and produce a nice unordered list = in
>>> html. Until the moment I updated to the
>>> current development version:
>>>
>>> Org-mode version 8.3.4 (release_8.3.4-588-g924431 @ /home/lipa= ri/elisp/org-mode/lisp/)
>>>
>>> Now, it produces the attached screenshot:
>>>
>>> snapshot
>>>
>>> Hence my question: what happened to ":wrap HTML" ?? = Is there an equivalent way to express the same
>>> behaviour as before?
>>>
>>
>> I bet :wrap HTMP produces
>>
>> #+BEGIN_HTML
>> ...
>> #+END_HTML
>>
>> instead of
>>
>> #+BEGIN_EXPORT HTML
>> #+END_EXPORT
>
> So I guess the OP should write :wrap export HTML.
>
> We could also add the export part automatically, but that would limit<= br> > the value of the parameter (e.g., impossible to do anything else than<= br> > export blocks)

We need to allow special blocks.=C2=A0 But the question is whether we can "guess" when something is a backend and do the right thing.=C2=A0= It=E2=80=99s probably
a "can of worms" to try to guess.

Rasmus

--
Nothing's wrong with an email that ends in a minor key


--94eb2c05aff6fffd02052c940723--