From: Kenichi Handa <handa@m17n.org>
To: "S.P.Tseng" <deftsp@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs crash when open some newsgroups with gnus
Date: Thu, 18 Sep 2008 16:42:36 +0900 [thread overview]
Message-ID: <E1KgE9s-0004s2-6h@etlken.m17n.org> (raw)
In-Reply-To: <85ej3jm5uw.fsf@modprobe.cn> (deftsp@gmail.com)
In article <85ej3jm5uw.fsf@modprobe.cn>, "S.P.Tseng" <deftsp@gmail.com> writes:
> I think I have found the reason.
> After execute '(define-coding-system-alias 'gbk 'gb2312)', charset gbk will be
> treated as charset gb2312. Emacs22 do not have the charset gbk, so that will be
> fine. But Emacs23 support both. You know the charset gbk is bigger than gb2312,
> when some char belong to charset gbk but be treated as gb2312 it will cause
> overflow.
Coding system and charset are different concepts in Emacs,
and as far as I remember, I designed coding system in Emacs
23 not to crash even if one does (define-coding-system-alias
'gbk 'gb2312). If it crashes in your case, there's a bug.
But, I can't reproduce the crash. So, could you please find
where Emacs crashes, or show me an exact recipe to reproduce
the crash.
> How about when execute (define-coding-system-alias A B), if charset A is bigger than B,
> give some warning or refuse?
It may be a solution but at first I want to know which code
is wrong.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-09-18 7:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 8:21 emacs crash when open some newsgroups with gnus S.P.Tseng
2008-09-08 8:28 ` S.P.Tseng
2008-09-09 6:23 ` S.P.Tseng
2008-09-16 9:40 ` S.P.Tseng
2008-09-16 11:20 ` Kenichi Handa
2008-09-16 12:10 ` S.P.Tseng
2008-09-17 5:43 ` Kenichi Handa
2008-09-17 10:20 ` S.P.Tseng
2008-09-18 7:42 ` Kenichi Handa [this message]
2008-09-18 10:20 ` S.P.Tseng
2008-09-18 11:59 ` Kenichi Handa
2008-09-18 12:33 ` S.P.Tseng
2008-09-19 1:17 ` Kenichi Handa
2008-09-19 3:12 ` S.P.Tseng
2008-09-25 12:32 ` Kenichi Handa
2008-09-25 12:51 ` S.P.Tseng
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1KgE9s-0004s2-6h@etlken.m17n.org \
--to=handa@m17n.org \
--cc=deftsp@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).