Re: [Evolution-hackers] Heads Up: More Camel API breakage in 2.31

2010-07-11 Thread David Woodhouse
On Thu, 2010-07-08 at 11:58 -0400, Matthew Barnes wrote: I finally finished converting Camel's error handling code to GError. CamelException is no more. I plan to push this later today after a bit more testing. It will debut in 2.31.5 along with another libcamel soname increment. I note

Re: [Evolution-hackers] Heads Up: More Camel API breakage in 2.31

2010-07-11 Thread Matthew Barnes
On Sun, 2010-07-11 at 13:08 +0100, David Woodhouse wrote: I note that in some places you've elected not to propagate the error pointer. For example in imapx_parse_status_info(): -imapx_parse_status_info (struct _CamelIMAPXStream *is, CamelException *ex) +imapx_parse_status_info (struct

Re: [Evolution-hackers] imapx: Avoid running FETCH_NEW_MESSAGES and REFRESH_INFO jobs simultaneously

2010-07-11 Thread David Woodhouse
On Sun, 2010-07-11 at 15:11 +0100, David Woodhouse wrote: From 1d1b146e58f918f67ccff93c4fb5388429bf12e7 Mon Sep 17 00:00:00 2001 From: David Woodhouse david.woodho...@intel.com Date: Sun, 11 Jul 2010 15:11:17 +0100 Subject: [PATCH] imapx: Avoid running FETCH_NEW_MESSAGES and REFRESH_INFO

Re: [Evolution-hackers] Evo won't display special characters

2010-07-11 Thread David Woodhouse
On Sat, 2010-04-17 at 23:13 -0400, Paul Smith wrote: I understand that this is very likely an invalid message and that \224 is a bogus character in an iso-8859-1 charset. No, it's a valid character in ISO8859-1. But your message isn't being interpreted as ISO8859-1. Its Content-Type: header

Re: [Evolution-hackers] Evo won't display special characters

2010-07-11 Thread David Woodhouse
On Sun, 2010-07-11 at 16:00 +0100, David Woodhouse wrote: We seem to be ignoring the META HTTP-EQUIV... tag in the HTML itself, which is trying to override the Content-Type: header and _is_ correctly specifying the character set. Hrm. That _is_ actually supported by gtkhtml, but evolution