From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Double encoding in ~/Mail/active
Date: Sun, 01 Aug 2010 13:13:04 +0200 [thread overview]
Message-ID: <87tynemvr3.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <b4mr5ii7g6l.fsf@jpl.org>
On Sun, 01 Aug 2010 19:58:26 +0900, Katsumi wrote:
> Sorry for enbugging. I'm going to fix it asap.
Great!
> Maybe I have to make it encode nnml group names conditionally.
I didn't quite understand the changes you made (but that is not saying
much, I am a elisp newbie still).
Doesn nnmail-active-file-coding-system come in to play here somehow?
Best regards,
Adam
--
"The laws of perspective have been repealed! Adam Sjøgren
Objects no longer diminish in size with distance!" asjo@koldfront.dk
next prev parent reply other threads:[~2010-08-01 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 14:03 Stack overflow: Stack overflow in regexp matcher Adam Sjøgren
2010-07-31 22:02 ` Adam Sjøgren
2010-08-01 5:25 ` Adam Sjøgren
2010-08-01 7:55 ` Double encoding in ~/Mail/active Adam Sjøgren
2010-08-01 10:58 ` Katsumi Yamaoka
2010-08-01 11:13 ` Adam Sjøgren [this message]
2010-08-02 0:14 ` Katsumi Yamaoka
2010-08-02 21:43 ` Adam Sjøgren
2010-08-02 23:21 ` Katsumi Yamaoka
2010-08-03 5:54 ` Adam Sjøgren
2010-08-04 0:38 ` Katsumi Yamaoka
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=87tynemvr3.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).