Re: [Bug] Verbatim code gets interpreted

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

-- 
Sébastien Vauban