From: Matt Price <moptop99@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Yehonathan Sharvit <viebel@gmail.com>,
Org Mode <emacs-orgmode@gnu.org>, Rasmus <rasmus@gmx.us>
Subject: Re: allow live execution of code snippets in html export
Date: Thu, 15 Dec 2016 10:50:22 -0500 [thread overview]
Message-ID: <CAN_Dec-S62Ms7wyG-VzqE81Dj4DFvfKCo6pyrmTFs2=Qc3fs3g@mail.gmail.com> (raw)
In-Reply-To: <87d1gtfqum.fsf@bzg.fr>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
On Thu, Dec 15, 2016 at 5:07 AM, Bastien <bzg@gnu.org> wrote:
> Hi Matt,
>
> Matt Price <moptop99@gmail.com> writes:
>
> > Would we need a switch to permit the old syntax for people with
> > complex setups who don't want to change?
>
> Yes. We need to be more careful on being backward compatible.
>
> The new patch in that other thread does this.
> > - make src-clojure in <pre class="src src-clojure"> customizable
> > ?
> >
> > Is this likely to break anything in derived exporters? It would
> > certianly be convenient e.g for using highlight.js in wordpress in
> > similar environments.
>
> Yes.
>
> > This seems like a good idea and pretty easy.
>
> I will think more about this.
>
> > I odn't really quite understand the problem and solution parameters.
> > Since Yehonathan is here on this thread and enthusiastic about
> > helping out: is there something he could do to make this feasible for
> > us? Or by "more general mechanism" do you mean some third way
> > between bundling and linking to?
>
> One way to solve this on Yehonathan's side is to update klipse.js and
> follow the instruction on librejs on how to make librejs accept the js
> code as "safe":
>
> https://www.gnu.org/software/librejs/free-your-javascript.html
>
> I don't know how much work is involved in this, though.
>
I think you just have to add two lines to non-minified scripts, and one
more to minified scripts:
https://www.gnu.org/software/librejs/free-your-javascript.html#magnet-link-license
Yehonathan, would you bewilling to do this?
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 3132 bytes --]
next prev parent reply other threads:[~2016-12-15 15:51 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
2016-12-15 3:18 ` Matt Price
2016-12-15 10:07 ` Bastien
2016-12-15 15:50 ` Matt Price [this message]
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='CAN_Dec-S62Ms7wyG-VzqE81Dj4DFvfKCo6pyrmTFs2=Qc3fs3g@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=bzg@gnu.org \
--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).