unwanted html in email/feeds

[Sharon Kimble]

I'm having the odd problem in that when I view an email/rss feed
postings it is showing with html content, like this -

--8<---------------cut here---------------start------------->8---
<p> A few days ago, for no reason (for fun, maybe), I cloned the Github mirror of Emacs and built a latest Emacs. I also
removed my old Emacs (I was silly, I blame Melbourne's weather :D). Many subtle problems occurred since then,
for example, executing <code>org-html-export-as-html</code> often causes the following error: </p> <div
class="org-src-container"> <pre class="src src-text">org-html-fontify-code: Wrong number of arguments: #[(_beg _end)
"???" [font-lock-fontify-buffer] 1], 0 </pre> </div> <p><span id="more-781"></span></p> <div
id="outline-container-sec-1" class="outline-2"> <h2 id="sec-1"><span class="section-number-2">1</span> Solution</h2> <div
class="outline-text-2" id="text-1"> <p> Redefine function <code>org-font-lock-ensure</code>. Add the following code snippet
to <i>init.el</i> and execute it to solve the problem: </p> <div class="org-src-container"> <pre class="src
--8<---------------cut here---------------end--------------->8---

Which is really awkward, but it is showing in the mini-buffer -

╭────
│gnus-summary-highlight-line: Wrong type argument: consp, nil
╰────

I've checked in my .gnus and there is *no* mention made of "highlight",
however the following shows in my 'custom.el'

--8<---------------cut here---------------start------------->8---
'(highlight-changes-colors (quote ("#FD5FF0" "#AE81FF")))
'(highlight-tail-colors
(quote
(("#073642" . 0)
("#546e00" . 20)
("#00736f" . 30)
("#00629d" . 50)
("#7b6000" . 60)
("#8b2c02" . 70)
("#93115c" . 85)
("#073642" . 100))))
--8<---------------cut here---------------end--------------->8---

So how do I put it right please?

Thanks
Sharon.

[Lars Ingebrigtsen]

Post by Sharon Kimble
Which is really awkward, but it is showing in the mini-buffer -
╭────
│gnus-summary-highlight-line: Wrong type argument: consp, nil
╰────

Try setting `debug-on-error' to t and post the resulting backtrace when
this happens.