From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: problem reading gwene feeds in gnus agent
Date: Fri, 13 May 2011 10:52:07 +0100 [thread overview]
Message-ID: <87hb8zapx4.fsf@ucl.ac.uk> (raw)
In-Reply-To: <878vuc5az5.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 12 May 2011 08:01:34 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Thu, 05 May 2011 19:05:46 +0100 Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> ESF> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> On Thu, 05 May 2011 08:46:56 +0100 Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>>>
> ESF> ... continuing problems with reading HTML emails in development gnus:
> ESF> I mentioned a couple of days ago problems reading gwene postings; I also
> ESF> have more generally problems reading HTML content emails when offline
> ESF> using the gnus agent. If there is alternative content, I can access the
> ESF> text version (which is the default in my case) but not the HTML version.
> ESF> Some emails have no text alternative and, in those cases, I get:
>>>
> ESF> ,----
> ESF> | not: Wrong type argument: listp, shr-link
> ESF> `----
>>>
>>> Ugh, sorry. That's my bug in `shr-urlify' but I don't know how to fix
>>> it properly. Lars, can you please look at it or I will just remove that
>>> change to `shr-urlify'.
>
> ESF> Okay, thanks! It's not a deal breaker (usually, html only messages are
> ESF> those I can typically ignore ;-).
>
> Julien Danjou fixed this, thanks go to him!
>
> Ted
>
>
Indeed, thanks Julien: things seem to be working just fine now!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.18
prev parent reply other threads:[~2011-05-13 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 16:43 Eric S Fraga
2011-05-05 7:46 ` Eric S Fraga
2011-05-05 15:53 ` Ted Zlatanov
2011-05-05 18:05 ` Eric S Fraga
2011-05-12 13:01 ` Ted Zlatanov
2011-05-13 9:52 ` Eric S Fraga [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hb8zapx4.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).