Re: Emacs 23.1.93 pretest

[Kenichi Handa <handa@m17n.org>]

In article <83zl2q30pa.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> The problem was in two places: in emacs_mule_char and in
> decode_coding_emacs_mule (which calls emacs_mule_char).
> emacs_mule_char called DECODE_CHAR, which could result in a call to
> decode_char, which could call load_charset_map_from_file (through
> load_charset).  Both emacs_mule_char and decode_coding_emacs_mule walk
> through buffer text with pointers, and those need to be fixed-up after
> the call to load_charset_map_from_file.

> I replaced the call to DECODE_CHAR with CODING_DECODE_CHAR, which
> wraps DECODE_CHAR with code that fixes up the pointers to buffer text
> if a charset map was loaded by DECODE_CHAR.  decode_coding_emacs_mule
> needed a similar fixup for its own pointers to buffer text.

> This is now fixed in the repository.  I think this fixes the original
> problem; at least my .emacs.desktop file with a Latin-2 character now
> loads correctly, both in the MS-Windows build and in the MS-DOS build.

Thank you for fixing it.

> Perhaps Handa-san could look at the two other callers of DECODE_CHAR
> in coding.c, and see if they, too, need to be replaced with
> CODING_DECODE_CHAR.

Two other callers of DECODE_CHAR Fdecode_sjis_char and
Fdecode_big5_char, and they are ok.

---
Kenichi Handa
handa@m17n.org