From: Ricardo Wurmus <rekado@elephly.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 45015@debbugs.gnu.org
Subject: bug#45015: [mumi] 44964 cannot be displayed
Date: Sun, 06 Dec 2020 12:30:08 +0100 [thread overview]
Message-ID: <87360j6ukf.fsf@elephly.net> (raw)
In-Reply-To: <87360lnz1n.fsf@systemreboot.net>
Arun Isaac <arunisaac@systemreboot.net> writes:
>> For some reason “Jorge P. de Morais Neto <jorge+list@disroot.org>” is
>> not split up into name and address parts but remains a single string.
>
> I have fixed this bug in the latest guile-email master, and added
> tests to prevent regression. See
> https://git.systemreboot.net/guile-email/commit/?id=37e245539bc9e27db35731e7b517cdde397834e2
> and
> https://git.systemreboot.net/guile-email/commit/?id=907a5d678c58eff653133df441aeecd3b7025e37
Thank you! You are always very fast and thorough; I appreciate this a lot!
>> Mumi commit 6fd49e9341d5673b70edfb333a4e5fa0a44128d2 works around this
>> problem, which I suspect might be a bug in guile-email.
>
> guile-email should guarantee the parsed From header is an alist of the
> appropriate form. So, I vote for reverting this commit, thus reducing
> complexity on mumi's end.
I agree. I wasn’t sure how difficult it would be to fix it in
guile-email, so I added the workaround just in case it takes longer.
I’ll upgrade and revert that commit soon.
--
Ricardo
next prev parent reply other threads:[~2020-12-06 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 20:26 bug#45015: [mumi] 44964 cannot be displayed Ricardo Wurmus
[not found] ` <handler.45015.B.16069407982867.ack@debbugs.gnu.org>
2020-12-04 5:59 ` Ricardo Wurmus
2020-12-04 19:36 ` Arun Isaac
2020-12-06 11:30 ` Ricardo Wurmus [this message]
2020-12-06 11:50 ` Arun Isaac
2020-12-04 6:11 ` Arun Isaac
2020-12-04 7:27 ` 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=87360j6ukf.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=45015@debbugs.gnu.org \
--cc=arunisaac@systemreboot.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.