GNU bug report logs - #11073
24.0.94; BIDI-related crash in redisplay with certain byte sequences

Previous Next

Package: emacs;

Reported by: Eli Zaretskii <eliz <at> gnu.org>

Date: Fri, 23 Mar 2012 11:27:02 UTC

Severity: normal

Found in version 24.0.94

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #47 received at 11073 <at> debbugs.gnu.org (full text, mbox):

From: Kenichi Handa <handa <at> m17n.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: eliz <at> gnu.org, 11073 <at> debbugs.gnu.org
Subject: Re: bug#11073: 24.0.94;
	BIDI-related crash in redisplay with certain byte sequences
Date: Wed, 04 Apr 2012 09:07:02 +0900
In article <jwvr4w5vuka.fsf-monnier+INBOX <at> gnu.org>, Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

> But isn't this (unify-charset 'big5 "MyBig5.map") performed in the
> .emacs?

Usually yes.  But, in that case, if .emacs is encoded in
Big5 and it contains some Big5 PUA chars, they are not
unified while loading .emacs.

> Is it really important to support adding unification rules
> after decoding took place?  If so, why?

As I wrote, I can't tell how important it is.  It may be
very important for those (but I guess very few) who need the
above operation, but not important for the majority.

I'm ok to remove such a feature if the maintainers decide
that.

> And also, what about removing unification rules after
> decoding?

When one tells Emacs to unify some chars, and then reads a
file containing those chars, there's no way to dis-unify
them.

---
Kenichi Handa
handa <at> m17n.org




This bug report was last modified 12 years and 95 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.