emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Bug] Verbatim code gets interpreted
Date: Mon, 07 Mar 2011 16:30:49 +0100	[thread overview]
Message-ID: <87pqq3yml2.fsf@gnu.org> (raw)
In-Reply-To: <80lj0rpd5r.fsf@somewhere.org> (=?iso-8859-1?Q?=22S=E9bastien?= Vauban"'s message of "Mon, 07 Mar 2011 09:06:56 +0100")

Hi Sébastien,

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> #+begin_html
> <div id="disqus_thread"></div>
> <script type="text/javascript">
>     (function() {
>         var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
>         dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
>         (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
>     })();
> </script>
> #+end_html
> But the [0] gets interpreted as a footnote... which is not found, hence an
> error on the page, and the JS code is not usable.
> [...]
> But I wanted to report this finding.

Thanks for reporting this.  I think we could rewrite the export
preprocess function to allow export parameters to be added:

| #+begin_html ^:nil 
| ...
| #+end_html

In such a block, the ^:nil option would take precedence over the
possibly ^:t option in the buffer.  I'll have a look into this for 
the next release.



  reply	other threads:[~2011-03-07 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07  8:06 [Bug] Verbatim code gets interpreted Sébastien Vauban
2011-03-07 15:30 ` Bastien [this message]
2011-03-08 16:02   ` Sébastien Vauban

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:

  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=87pqq3yml2.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \


* 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


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).