From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: Cannot forward messages: no such coding system - koi8-r
Date: 03 May 2000 09:34:13 -0400 [thread overview]
Message-ID: <87u2gflpuy.fsf@lucy.mtth1.on.wave.home.com> (raw)
In-Reply-To: Dmitry Yaitskov's message of "03 May 2000 01:20:54 -0400"
After cvs update this morning, I again can mail using 5.8.7 (thanks!)
but I still can not mail forward. Any ideas?
Dmitry Yaitskov <dimas@home.com> wrote:
> Shenghuo ZHU <zsh@cs.rochester.edu> wrote:
>
> > >>>>> "Dmitry" == Dmitry Yaitskov <dimas@home.com> writes:
> >
> > Dmitry> Shenghuo ZHU <zsh@cs.rochester.edu> wrote:
> > >> >>>>> "DY" == Dmitry Yaitskov <dimas@home.com> writes:
> > >>
> > DY> Hi,
> > DY> This problem is in gnus-5.8.6. It was not present in 5.8.2 and
> > DY> earlier.
> > >>
> > DY> The problem occurs when I try to mail forward anything. I am using
> > DY> XEmacs 21.2.b32 *without* MULE, have message-default-charset set to
> > DY> koi8-r. It all worked just fine till recently, in 5.8.4 there were
> > DY> similar problems when I tried to forward messages containing
> > DY> `Content-Type: text/plain; charset=koi8-r' as one of the headers (I
> > DY> could forward after deleting that header), but now I'm stuck - I
> > DY> cannot forward any messages at all. (Sending works fine even with
> > DY> koi8-r). Please, I'll appreciate any ideas. Thanks.
> > >>
> > >> Could you (setq debug-on-error t) and send the backtrace?
> >
> > Dmitry> Here it is:
> >
> > Dmitry> Signaling: (error "No such coding system" koi8-r)
> > Dmitry> mm-encode-coding-region(1 816 koi8-r)
> >
> > [...]
> >
> >
> > I've located the bug. Please check out the latest CVS version and test
> > it again.
>
> After updating gnus from CVS to 5.8.7, I can't not only forward, but
> even simply post messages. With the same error (no such coding system:
> koi8-r). When forwarding, I got exactly same backtrace. I had to
> revert to 5.8.6 to post this message.
--
Cheers,
-Dima.
next prev parent reply other threads:[~2000-05-03 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 16:06 Dmitry Yaitskov
2000-05-02 16:41 ` Shenghuo ZHU
2000-05-02 19:13 ` Dmitry Yaitskov
2000-05-03 2:06 ` Shenghuo ZHU
2000-05-03 5:20 ` Dmitry Yaitskov
2000-05-03 13:34 ` Dmitry Yaitskov [this message]
2000-05-03 15:56 ` Shenghuo ZHU
2000-05-03 17:55 ` Dmitry Yaitskov
2000-05-03 18:49 ` Shenghuo ZHU
2000-05-03 20:04 ` Dmitry Yaitskov
2000-05-03 20:21 ` Shenghuo ZHU
2000-05-03 21:50 ` Dmitry Yaitskov
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=87u2gflpuy.fsf@lucy.mtth1.on.wave.home.com \
--to=dimas@home.com \
/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).