guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <>
To: Ricardo Wurmus <>
Subject: Re: guile email: decoding error
Date: Sun, 01 Dec 2019 00:43:17 +0530	[thread overview]
Message-ID: <> (raw)
Message-ID: <20191130191317.ZjVl-A4SZu0vIAe30FoGx2s8OCQ51H4XN9qVg85tLkg@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

>> Could you try again with this latest fix and let me know if it works?
> The latest version of guile-email fixes all problems I had.  Bug 37444
> renders correctly now, as does bug 37978.

That's nice! :-)

> Thank you very much!  I’ll update mumi soon to use the latest version of
> guile-email.


> Aside; I’ve been having weird problems with the web server from (fibers
> web server).  Using that web server somehow breaks XML parsing in my
> recent tests.  Every XML processing outside of the web server loop works
> just fine.  Very odd.

Very odd indeed. But I don't know enough about the fibers web server to
contribute any meaningful insight. Perhaps this is something to do with
thread safety of the XML parser?

> (This problem contributed to the delay in testing your improvements,
> but really the biggest problem was making enough time to sit down
> without the baby as I can’t type well enough with just one free arm.)

I understand. Family comes first! :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-11-30 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-10-01 20:10 ` [guile-email] " Arun Isaac
2019-10-01 20:10   ` Arun Isaac
2019-10-22 16:41   ` [guile-email] " Arun Isaac
2019-10-22 16:41     ` Arun Isaac
2019-11-29 12:39   ` Ricardo Wurmus
2019-11-30 19:13     ` Arun Isaac [this message]
2019-11-30 19:13       ` Arun Isaac

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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