From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: what happened to :wrap HTML ?
Date: Wed, 24 Feb 2016 23:56:09 +0100 [thread overview]
Message-ID: <87ziup67li.fsf@gmx.us> (raw)
In-Reply-To: 87mvqp4tdw.fsf@nicolasgoaziou.fr
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
next prev parent reply other threads:[~2016-02-24 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 20:45 what happened to :wrap HTML ? Giuseppe Lipari
2016-02-24 20:56 ` Nick Dokos
2016-02-24 22:48 ` Nicolas Goaziou
2016-02-24 22:56 ` Rasmus [this message]
2016-02-25 8:32 ` Giuseppe Lipari
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=87ziup67li.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/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).