From: Joao Cachopo <joao@cachopo.org>
To: ding@gnus.org
Subject: Re: Make rfc2231-decode-encoded-string more robust
Date: Fri, 30 May 2008 11:25:51 +0100 [thread overview]
Message-ID: <m2skw0ulzk.fsf@cachopo.org> (raw)
In-Reply-To: <b4mfxs014xv.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> I think that function should never stop Gnus whatever happens;
> at least things other than the attachment in question should be
> displayed. Thank you for the patch, but I've modified it in
> another way in the Gnus trunk. It ignores things that are not
> 2-digit hexadecimal characters that follow `%'s.
That's fine, provided that it solves the problem.
I've still not checked your change, but it's not clear from your
description that you deal with the case where the '%' is at the end of
the string. That is, there is nothing following it. That's what was
causing the errors that I've seen.
Best regards,
--
João Cachopo
next prev parent reply other threads:[~2008-05-30 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 20:22 Joao Cachopo
2008-05-30 10:06 ` Katsumi Yamaoka
2008-05-30 10:25 ` Joao Cachopo [this message]
2008-05-30 10:32 ` Katsumi Yamaoka
2008-05-30 10:40 ` Joao Cachopo
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=m2skw0ulzk.fsf@cachopo.org \
--to=joao@cachopo.org \
--cc=ding@gnus.org \
/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;
as well as URLs for NNTP newsgroup(s).