From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: No "Content-Type:"
Date: 17 Jan 2000 05:19:19 -0500 (EST) [thread overview]
Message-ID: <yosuya9pm254.fsf@jpl.org> (raw)
In-Reply-To: Katsumi Yamaoka's message of "17 Jan 2000 05:12:33 -0500 (EST)"
Oops,
>>>>> In <yosuu2kd80ry.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> (setq gnus-group-charset-alist
> (cons '("^some\\.japanese\\.list$" . 'iso-2022-jp-2)
> gnus-group-charset-alist))
Sorry, the correct way is below:
(setq gnus-group-charset-alist
(cons '("^some\\.japanese\\.list$" iso-2022-jp-2)
gnus-group-charset-alist))
--
~{I=8T?KC@~} <yamaoka@jpl.org>
next prev parent reply other threads:[~2000-01-17 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 18:27 Shigeki Uno
2000-01-16 22:23 ` Kai Großjohann
2000-01-17 8:32 ` Shigeki Uno
2000-01-17 0:31 ` Katsumi Yamaoka
2000-01-17 9:17 ` Kai Großjohann
2000-01-17 10:12 ` Katsumi Yamaoka
2000-01-17 10:19 ` Katsumi Yamaoka [this message]
2000-01-17 11:52 ` Shigeki Uno
2000-01-17 6:48 ` Michael Welsh Duggan
2000-01-17 13:15 ` Solved (was: Re: No "Content-Type:") Shigeki Uno
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=yosuya9pm254.fsf@jpl.org \
--to=yamaoka@jpl.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).