From: Steinar Bang <sb@dod.no>
Subject: Message "Unknown charset: us-ascii" when entering nnimap group
Date: Sat, 10 Dec 2005 19:18:34 +0100 [thread overview]
Message-ID: <87vexw4xz9.fsf@dod.no> (raw)
Platform: Intel Pentium M, debian sarge
GNU Emacs 21.4.1,
No Gnus v0.4 (today's CVS)
When entering a particular agentizedized nnimap group, I get the
message
Unknown charset: us-ascii
in the minibuffer, and then Gnus seems to freeze for a little while
before continuing and entering the group.
The *Messages* lines for entering the group, are:
Retrieving newsgroup: nnimap+doohan:INBOX...
nnimap: Updating info for nnimap+doohan:INBOX...
nnimap: Updating info for nnimap+doohan:INBOX...done
Fetching headers for nnimap+doohan:INBOX...
Unknown charset: us-ascii
Fetching headers for nnimap+doohan:INBOX...done
Generating summary...done
No more unread articles
When I grep the .overview file, of that agentized group I find only
one match for 'us-ascii', and that is:
10449 =?us-ascii?Q?SV=3A_Priser_pa_Ventura=3F?= AMD motorsykler AS <amd@amd.no> Sat, 12 Jun 2004 12:46:16 +0200 <01C4507B.40FC69E0.amd@amd.no> 2378 27 Xref: localhost.localdomain INBOX:10449 To: "'Steinar Bang'" <sb@dod.no>
Ie. an RFC2047 coded subject that doesn't need it, because it has
charset us-ascii.
I haven't debugged to see if it actually gets there, but I'm guessing
this is output by the statement in (rfc2047-decode-encoded-words) on
line 828 of rfc2047.el, because this is a fairly new piece of code
checked in in version 7.44 of the file, on October 19 of this year,
and this didn't happen in the old version I used (CVS checkout from
April of 2005).
I will investigate further.
next reply other threads:[~2005-12-10 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 18:18 Steinar Bang [this message]
2005-12-12 1:55 ` Katsumi Yamaoka
2005-12-12 9:21 ` Steinar Bang
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=87vexw4xz9.fsf@dod.no \
--to=sb@dod.no \
/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).