From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Feature freeze on October 1 Date: Fri, 21 Sep 2012 15:40:59 +0300 Message-ID: <83ehlvy2ec.fsf@gnu.org> References: <87fw6izq6z.fsf@gnu.org> <83zk4o1vli.fsf@gnu.org> <83y5k81pcx.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1348231265 24013 80.91.229.3 (21 Sep 2012 12:41:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Sep 2012 12:41:05 +0000 (UTC) Cc: handa@gnu.org, cyd@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 21 14:41:10 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TF2Xc-0007gx-QD for ged-emacs-devel@m.gmane.org; Fri, 21 Sep 2012 14:41:08 +0200 Original-Received: from localhost ([::1]:36791 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TF2XY-0007Dr-9V for ged-emacs-devel@m.gmane.org; Fri, 21 Sep 2012 08:41:04 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:36345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TF2XQ-0006sA-4d for emacs-devel@gnu.org; Fri, 21 Sep 2012 08:41:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TF2XI-0008II-Bu for emacs-devel@gnu.org; Fri, 21 Sep 2012 08:40:56 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:59815) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TF2XF-0008HK-Ed; Fri, 21 Sep 2012 08:40:45 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MAP00G009F8ZN00@a-mtaout22.012.net.il>; Fri, 21 Sep 2012 15:40:43 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MAP00G7O9VVY830@a-mtaout22.012.net.il>; Fri, 21 Sep 2012 15:40:43 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:153432 Archived-At: > From: Stefan Monnier > Cc: handa@gnu.org, cyd@gnu.org, emacs-devel@gnu.org > Date: Mon, 17 Sep 2012 15:36:42 -0400 > > >> AFAIK unification is already performed when we read a char from > >> outside Emacs > > Where does that happen in the code? > > I assume it's done in the coding-system's decoding code. But that doesn't get run (or at least not always) when a character is typed on the keyboard, does it? E.g., on MS-Windows characters are read directly in Unicode when possible. I'm sure Emacs does something like that on X as well. So it looks like some un-unified characters can still sneak into the buffer. > so maybe all it takes is to remove the maybe_unify_char thingy? Not sure that's all. I hope Handa-san could outline the plan for attacking this problem, then maybe I could work on at least part of that, if not all of it.