From: Steinar Bang <sb@dod.no>
Subject: Re: Lost rfc2047 decoding in the summary buffer (test æøå)
Date: Thu, 28 Dec 2006 08:51:20 +0100 [thread overview]
Message-ID: <87irfwlapz.fsf@bang.priv.no> (raw)
In-Reply-To: <87r6uklc88.fsf@bang.priv.no>
>>>>> Steinar Bang <sb@dod.no>:
> Platform: Intel Pentium M,
> Ubuntu Dapper,
> emacs21 21.4a-3ubuntu2,
> No Gnus v0.6 (CVS update from yesterday)
> I updated from CVS yesterday, for the first time since May 1. And
> then Gnus stopped decoding RFC2047 in the subject fields (this
> article has RFC2047 coding in the headers and will hopefully trigger
> the issue with me).
Yes, it does.
next prev parent reply other threads:[~2006-12-28 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 7:18 Steinar Bang
2006-12-28 7:51 ` Steinar Bang [this message]
2006-12-28 8:42 ` Reiner Steib
2006-12-28 14:48 ` Steinar Bang
2006-12-28 15:35 ` Reiner Steib
2006-12-30 11:04 ` Steinar Bang
2006-12-30 12:16 ` Reiner Steib
2006-12-30 12:37 ` Steinar Bang
2006-12-30 13:27 ` 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=87irfwlapz.fsf@bang.priv.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).