Hi there,
On Fri, 24 Oct 2014, Patrick O'Callaghan wrote:
... the easiest solution is not to use digests, which are a hangover
from the distant past and provide no benefit nowadays.
I see no problem; equally I see no need for any solution.
I'm the one to decide what benefits I derive from di
On Fri, 2014-10-24 at 13:07 +0100, G.W. Haywood wrote:
> Hi there,
>
> On Fri, 24 Oct 2014, Patrick O'Callaghan wrote:
>
> > ... the easiest solution is not to use digests, which are a hangover
> > from the distant past and provide no benefit nowadays.
>
> I see no problem; equally I see no need
Each of your emails have created a new thread, Ged.
In cronological order:
Your email
contains:
> In-Reply-To:
> References:
but it was a reply to <1414029104.2922.3.ca...@centurylink.net> so
should have contained that.
Your email
contains:
> In-Reply-To:
> References:
but it should hav
Ángel wrote:
> Apparently it is being marked as a reply to the digest, not to the
> individual message included on it.
(...)
> If at least you had stated what steps you were following for reply, or
> how digests helps you, maybe we could have suggested an even better
> procedure (eg based on the ml
The Junk folder shoes one unread mail. If I click the Junk folder,
Evolution segfaults while generating the message list.
[rocketmouse@archlinux ~]$ evolution
[snip]
(evolution:13377): GLib-GObject-CRITICAL **: g_closure_unref: assertion
'closure->ref_count > 0' failed
Segmentation fault (core du
On Sat, 2014-10-25 at 06:28 +0200, Ralf Mardorf wrote:
> The Junk folder shoes one unread mail. If I click the Junk folder,
^ shows ;)
> Evolution segfaults while generating the message list.
>
> [rocketmouse@archlinux ~]$ evolution
> [snip]
> (evolution:13377): GLib-GObject-C
