guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <>
To: Ricardo Wurmus <>
Subject: Re: [bug] Use decode-mime-encoded-word on subject?
Date: Sun, 21 Jul 2019 22:53:49 +0530	[thread overview]
Message-ID: <> (raw)
Message-ID: <20190721172349.dCzGqZ9ZdL4Cve7UKBN2OvjGVbOwc0vO18J5rX2XfGE@z> (raw)
In-Reply-To: <>

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

>> I see at 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
> bug report.

I have pushed a fix. See

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

  parent reply	other threads:[~2019-07-21 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-07-21 15:25 ` [guile-email] [Guile Email] " Arun Isaac
2019-07-21 15:25   ` Arun Isaac
2019-07-21 17:23   ` Arun Isaac [this message]
2019-07-21 17:23     ` [bug] " Arun Isaac
2019-07-21 17:43     ` Ricardo Wurmus

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