From: Christopher Baines <mail@cbaines.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] decoding-error crash
Date: Sun, 22 Sep 2019 14:19:46 +0100 [thread overview]
Message-ID: <87muew4gel.fsf@cbaines.net> (raw)
In-Reply-To: <cu7o8zk802f.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
Arun Isaac <arunisaac@systemreboot.net> writes:
>>>> 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 Arun, that definately fixes the issue with the email I sent
initially, although I think there might be other emails on the
guix-commits mailing list that still can't be read.
For testing, I downloaded
https://lists.gnu.org/archive/mbox/guix-commits/2019-08 and then tried
to read it with:
(map parse-email (call-with-input-file "2019-08" mbox->emails))
And I get a decoding-error backtrace.
In email/email.scm:
824:34 8 (parse-email _)
In rnrs/io/ports.scm:
334:0 7 (call-with-port #<input: string 4a80770> _)
In email/email.scm:
616:21 6 (_ #<input: string 4a80770>)
In email/utils.scm:
60:13 5 (read-while _ _ _)
In ice-9/ports.scm:
550:4 4 (call-with-output-string _)
In email/utils.scm:
52:13 3 (read-while-loop #<output: string 4a80690>)
91:14 2 (get-line-with-delimiter _)
In ice-9/rdelim.scm:
195:24 1 (read-line _ _)
In unknown file:
0 (%read-line #<input: string 4a80770>)
ERROR: In procedure %read-line:
Throw to key `decoding-error' with args `("peek-char" "input decoding error" 84 #<input: string 4a80770>)'.
Any ideas?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2019-09-22 15:00 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
2019-09-16 20:20 ` Arun Isaac
2019-09-22 13:19 ` Christopher Baines [this message]
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=87muew4gel.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=arunisaac@systemreboot.net \
--cc=guile-email@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox