From: Arun Isaac <firstname.lastname@example.org>
To: Ricardo Wurmus <email@example.com>
Subject: Re: [Guile Email] Use decode-mime-encoded-word on subject?
Date: Sun, 21 Jul 2019 20:55:31 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Message-ID: <20190721152531.C46f-9a8kmkpP-BxRjtQ2i5XQIIJW-H7-gFiVwM3_nc@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
> I see at https://issues.guix.gnu.org/issue/36374 that the subjects
> contain some encoding garbage. Can this be avoided by running
> decode-mime-encoded-word on the subject?
Yes, that would work. But, you shouldn't have to do that. guile-email
should do that internally. This is a bug. I'll fix it. Thanks for the
In general, you should never have to manually invoke any function
provided by guile-email other than parse-email. If you have to, it's
probably a bug in guile-email.
You will be able to use the bug fix in guile-email only from the next
version (v0.2). That might take a while. Or, perhaps I'll do a quick
bugfix release v0.1.1 in a week's time.
> BTW mumi now fetches the original email messages from Debbugs, bypassing
> the SOAP service to avoid the problem of truncated messages.
Ok, nice. :-)
We now have a mailing list -- email@example.com -- for
guile-email. You can post any guile-email bugs or any other matter to
that list. I have CCed this mail to the list.
I'm also working on writing up documentation for guile-email. See
tentative first steps at https://guile-email.systemreboot.net/manual (I
might have to change this URL in the future).
I also wrote a very simple one-page website for guile-email:
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next parent reply other threads:[~2019-07-21 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2019-07-21 15:25 ` Arun Isaac [this message]
2019-07-21 15:25 ` Arun Isaac
2019-07-21 17:23 ` [guile-email] [bug] " Arun Isaac
2019-07-21 17:23 ` Arun Isaac
2019-07-21 17:43 ` Ricardo Wurmus
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