guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <>
To: Jack Hill <>, Ricardo Wurmus <>
Subject: Re: Mumi now uses raw emails and Mu
Date: Mon, 22 Jul 2019 23:24:20 +0530	[thread overview]
Message-ID: <> (raw)
Message-ID: <20190722175420.jlosJqcgS3VLnsCe9X-PmLuKBDriCjKpCojsyZDS6vc@z> (raw)
In-Reply-To: <>

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

> With the currently deployed mumi, it looks like my mails in
> are still mangling the '’' after 
> Ludo, but in a different way than before.

Like Ricardo said, this is indeed a bug in guile-email, the same bug you
reported earlier, in fact. I haven't fixed it yet, but I'm working on
it. The fix is a little more involved than I expected. Currently,
guile-email takes the entire email as a string, parses it and returns
the results. This constrains all characters in the email to have the
same encoding (specifically the charset in email terminology). But, an
email can have characters of different encodings. Therefore it must be
treated as a string of bytes not a string of characters.

> place for me to start trying to debug and learning the mail processing 
> code paths in mumi.

Parsing the email is done by guile-email. I only have a little
documentation at this point (you can find it at So, you'll mostly have to
read the source code. There is a mailing list at Feel free to post any guile-email bugs or
questions to that list.

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

       reply	other threads:[~2019-07-22 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2019-07-22 17:54   ` Arun Isaac [this message]
2019-07-22 17:54     ` Arun Isaac
2019-07-22 17:54     ` 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