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évr. 2016 à 23:56, Rasmus <rasmus@gmx.us> a écrit :

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
> > Hello,
> >
> > Nick Dokos <ndokos@gmail.com> writes:
> >
> >> Giuseppe Lipari <giulipari@gmail.com> 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 "<ul> <li> first item</li>"
> >>> 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/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’s probably
> a "can of worms" to try to guess.
>
> Rasmus
>
> --
> Nothing's wrong with an email that ends in a minor key
>
>
>