emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Bug] Verbatim code gets interpreted
Date: Tue, 08 Mar 2011 17:02:08 +0100	[thread overview]
Message-ID: <80mxl561of.fsf@somewhere.org> (raw)
In-Reply-To: 87pqq3yml2.fsf@gnu.org

Hi Bastien,

> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> 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.

Such a behavior is OK for me (as who can do more can do less), but I wonder
why we simply don't treat the block between `#+begin/end_html' as verbatim,
without touching it at all?

Couldn't one do the same as what happens for the lines prefixed by `#+HTML'?

Best regards,

Sébastien Vauban

      reply	other threads:[~2011-03-08 16:02 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
2011-03-08 16:02   ` Sébastien Vauban [this message]

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=80mxl561of.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


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