From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] [bug] Use decode-mime-encoded-word on subject?
Date: Sun, 21 Jul 2019 22:53:49 +0530 [thread overview]
Message-ID: <cu7h87ffgii.fsf@systemreboot.net> (raw)
In-Reply-To: <cu7k1cbflzo.fsf@systemreboot.net>
[-- Attachment #1.1: Type: text/plain, Size: 460 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
> bug report.
I have pushed a fix. See
https://git.systemreboot.net/guile-email/commit/?id=7c6f220e95feb3bc79f48aca16b5ca691a561d97
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
[-- Attachment #2: Type: text/plain, Size: 110 bytes --]
--
guile-email mailing list
guile-email@systemreboot.net
https://lists.systemreboot.net/listinfo/guile-email
WARNING: multiple messages have this Message-ID
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [bug] Use decode-mime-encoded-word on subject?
Date: Sun, 21 Jul 2019 22:53:49 +0530 [thread overview]
Message-ID: <cu7h87ffgii.fsf@systemreboot.net> (raw)
Message-ID: <20190721172349.dCzGqZ9ZdL4Cve7UKBN2OvjGVbOwc0vO18J5rX2XfGE@z> (raw)
In-Reply-To: <cu7k1cbflzo.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 460 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
> bug report.
I have pushed a fix. See
https://git.systemreboot.net/guile-email/commit/?id=7c6f220e95feb3bc79f48aca16b5ca691a561d97
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-07-21 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lfwreepz.fsf@elephly.net>
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7h87ffgii.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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