From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Feature freeze on October 1 Date: Fri, 21 Sep 2012 12:34:31 -0400 Message-ID: References: <87fw6izq6z.fsf@gnu.org> <83zk4o1vli.fsf@gnu.org> <83y5k81pcx.fsf@gnu.org> <83ehlvy2ec.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348245287 21839 80.91.229.3 (21 Sep 2012 16:34:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Sep 2012 16:34:47 +0000 (UTC) Cc: handa@gnu.org, cyd@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 21 18:34:50 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 1TF6Bl-0000I5-BB for ged-emacs-devel@m.gmane.org; Fri, 21 Sep 2012 18:34:49 +0200 Original-Received: from localhost ([::1]:35984 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TF6Bg-0000i2-Sb for ged-emacs-devel@m.gmane.org; Fri, 21 Sep 2012 12:34:44 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:59314) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TF6Ba-0000fl-25 for emacs-devel@gnu.org; Fri, 21 Sep 2012 12:34:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TF6BW-0004RQ-4C for emacs-devel@gnu.org; Fri, 21 Sep 2012 12:34:37 -0400 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:54761) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TF6BU-0004Qm-NO; Fri, 21 Sep 2012 12:34:32 -0400 Original-Received: from faina.iro.umontreal.ca (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id q8LGYVYn018107; Fri, 21 Sep 2012 12:34:32 -0400 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id CC04CB404D; Fri, 21 Sep 2012 12:34:31 -0400 (EDT) In-Reply-To: <83ehlvy2ec.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Sep 2012 15:40:59 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-Received-From: 132.204.246.20 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:153437 Archived-At: >> 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? Coding-system decoding is sometimes applied to keyboard events (e.g. under ttys) but not always, indeed. > 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. Indeed, and that should be just fine, there's no need for additional unification if we already have a Unicode char. > So it looks like some un-unified characters can still sneak into the > buffer. The un-unified chars are those outside of Unicode, so it shouldn't be an issue. >> 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. Yup. Stefan