From: Bastien Guerry <bzg@bzg.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org, viebel@gmail.com
Subject: Re: allow live execution of code snippets in html export
Date: Wed, 14 Dec 2016 11:36:57 +0100 [thread overview]
Message-ID: <87d1gukd9y.fsf@bzg.fr> (raw)
In-Reply-To: <877f72zux4.fsf@gmx.us> (Rasmus's message of "Wed, 14 Dec 2016 11:06:47 +0100")
Hi all,
thanks for adding me to this discussion!
klipse + org works pretty much out of the box, which is really great.
I just tested it again with a mix of Scheme and Clojure blocks, both
can work together within the same HTML page.
That said, I think we can take this opportunity to slightly improve
how ox-html handles source code:
- why only <pre> and not <pre><code> ?
- make src-clojure in <pre class="src src-clojure"> customizable ?
- have ob-javascript.el to let ox-html know how to export js code?
- have org-html-js to easily allow adding js libraries at the bottom
of a page? Perhaps together with #+html_js and #+html_js_extra ?
>> If the license permits, and there's a precedent, we could bundle the
>> scripts with org.
I have no problem with this, but I'd rather think a more general
mechanism to embed scripts in general and get more flexibility in
css classes.
If we provide a straightforward solution, I don't think there is
a problem pointing to Google servers.
We might have a problem with recommending js code that does not
pass the https://www.gnu.org/software/librejs/ tests: that is,
we cannot recommend code that is not advertised the way librejs
recommends it should be advertized.
This is an annoying issue, but a real one I guess.
As long as Klipse + org is somehow available and documented,
I'll be very happy :)
--
Bastien
next prev parent reply other threads:[~2016-12-14 10:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 14:55 allow live execution of code snippets in html export Matt Price
2016-12-13 16:11 ` Rasmus
[not found] ` <CAN_Dec8cw4QNFhcS7G7ktuY-A9vQEUftKLX4fN9c1XJ1TjF0Wg@mail.gmail.com>
2016-12-14 10:06 ` Rasmus
2016-12-14 10:36 ` Bastien Guerry [this message]
2016-12-15 3:18 ` Matt Price
2016-12-15 10:07 ` Bastien
2016-12-15 15:50 ` Matt Price
2016-12-15 20:55 ` Yehonathan Sharvit
2016-12-18 3:25 ` Yehonathan Sharvit
2016-12-14 17:55 ` Matt Price
2016-12-14 21:07 ` Yehonathan Sharvit
2016-12-15 2:10 ` Bastien Guerry
[not found] <44cd312833be418b92f225baf0940026@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-12-13 15:39 ` Eric S Fraga
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=87d1gukd9y.fsf@bzg.fr \
--to=bzg@bzg.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
--cc=viebel@gmail.com \
/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).