Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Strange nov line (N)
Date: 25 Apr 2000 18:14:03 -0400	[thread overview]
Message-ID: <2npurd96c4.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Shigeki Uno's message of "Wed, 26 Apr 2000 06:29:25 +0900 (JST)"

>>>>> "Shigeki" == Shigeki Uno <shigeki@mediawars.ne.jp> writes:

Shigeki> Following is a sample I got. 
Shigeki> --- start of backtrace ---

Shigeki> Signaling: (coding-system-error iso-2022-jp-2)
Shigeki>   mm-decode-coding-region(1 45 iso-2022-jp-2)
Shigeki>   mail-decode-encoded-word-string("[netbsd,05423] Re: jp.netbsd.org still down?")
Shigeki>   gnus-get-newsgroup-headers()
Shigeki>   gnus-select-newsgroup("nnml:ML.netbsd-j" nil nil)
Shigeki>   gnus-summary-read-group-1("nnml:ML.netbsd-j" nil nil nil nil nil)
Shigeki>   gnus-summary-read-group("nnml:ML.netbsd-j" nil nil nil nil nil nil)
Shigeki>   gnus-group-read-group(nil)
Shigeki> * call-interactively(gnus-group-read-group)

Shigeki> --- end of backtrace ---

On your system, it seems that iso-2022-jp-2 is not a coding system. To
make sure this, could you eval (mm-coding-system-p 'iso-2022-jp-2)?

If it is nil, I think you use a different version of mule as I do.

Shigeki> (I also can't enter groups written in english only...)
Shigeki> What's wrong ? 

What are those groups? Are groups starting with jp or japan?

-- 
Shenghuo



  reply	other threads:[~2000-04-25 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-23 19:32 Shigeki Uno
2000-04-23 20:10 ` Shenghuo ZHU
2000-04-23 21:29   ` Shigeki Uno
2000-04-23 21:57     ` Shenghuo ZHU
2000-04-25 21:29       ` Shigeki Uno
2000-04-25 22:14         ` Shenghuo ZHU [this message]
2000-04-27 17:44           ` Shigeki Uno
2000-04-26  2:48         ` Katsumi Yamaoka
2000-04-27 17:41           ` Solved. (was: Re: Strange nov line (N)) 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=2npurd96c4.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).