From: Arun Isaac <arunisaac@systemreboot.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] decoding-error crash
Date: Tue, 17 Sep 2019 01:50:56 +0530 [thread overview]
Message-ID: <cu7o8zk802f.fsf@systemreboot.net> (raw)
Message-ID: <20190916202056._H0gCXiIW2ef2c6r3OpRHa1io8Ln4VN7yxdXVJRVbVc@z> (raw)
In-Reply-To: <cu7r24g8anm.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
>>> From: ludo@gnu.org (Ludovic Courtès)
>
> On the other hand, I just realized that this is a non-standard Emacs
> message mode parens style address described at
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Mail-Headers.html
> . guile-email aims to support these non-standard addresses. So, I think
> we can relax the requirement that email headers be strictly ASCII. I'll
> push a fix and let you know.
I've pushed a fix along with a test to prevent regression. See
https://git.systemreboot.net/guile-email/commit/?id=203c9c2ae39a4c64bfd9199bbc2deae03c347998
Could you use a git checkout of the master branch for your guile-email
deployment? Or would you rather I get a minor bugfix release out soon?
Thanks for reporting this bug and thanks for choosing guile-email! :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-09-16 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 12:57 Christopher Baines
2019-09-16 9:50 ` Arun Isaac
2019-09-16 9:50 ` Arun Isaac
2019-09-16 16:32 ` Arun Isaac
2019-09-16 16:32 ` Arun Isaac
2019-09-16 20:20 ` Arun Isaac [this message]
2019-09-16 20:20 ` Arun Isaac
2019-09-22 13:19 ` Christopher Baines
2019-09-23 5:21 ` Arun Isaac
2019-09-23 5:21 ` Arun Isaac
2019-09-23 7:30 ` Christopher Baines
2019-09-23 19:28 ` Arun Isaac
2019-09-23 19:28 ` Arun Isaac
2019-09-24 7:17 ` Christopher Baines
2019-09-16 20:55 ` Christopher Baines
2019-09-17 5:37 ` Arun Isaac
2019-09-17 5:37 ` 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:
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=cu7o8zk802f.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
--cc=mail@cbaines.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