From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; Cannot isearch for non-ascii chars with emacs -nw -Q Date: Wed, 27 Feb 2008 11:13:18 -0500 Message-ID: References: <87oda4d6h8.fsf@fastmail.fm> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1204128902 7524 80.91.229.12 (27 Feb 2008 16:15:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 27 Feb 2008 16:15:02 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, thorn+news@fastmail.fm To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 27 17:15:23 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JUOvp-0006oX-3w for ged-emacs-devel@m.gmane.org; Wed, 27 Feb 2008 17:14:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUOvI-0006gT-Hv for ged-emacs-devel@m.gmane.org; Wed, 27 Feb 2008 11:14:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUOuz-0006Uf-Pn for emacs-devel@gnu.org; Wed, 27 Feb 2008 11:14:05 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUOuy-0006U3-CS for emacs-devel@gnu.org; Wed, 27 Feb 2008 11:14:05 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUOuy-0006Ty-27 for emacs-devel@gnu.org; Wed, 27 Feb 2008 11:14:04 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JUOux-0005R9-VR for emacs-devel@gnu.org; Wed, 27 Feb 2008 11:14:04 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JUOux-0004Az-JP for emacs-pretest-bug@gnu.org; Wed, 27 Feb 2008 11:14:03 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JUOuu-0005Q5-Hv for emacs-pretest-bug@gnu.org; Wed, 27 Feb 2008 11:14:03 -0500 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JUOuu-0005Pt-8I for emacs-pretest-bug@gnu.org; Wed, 27 Feb 2008 11:14:00 -0500 Original-Received: from ceviche.home (vpn-132-204-232-211.acd.umontreal.ca [132.204.232.211]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id m1RGDxqj029116 for ; Wed, 27 Feb 2008 11:13:59 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id CD5DCB40C5; Wed, 27 Feb 2008 11:13:18 -0500 (EST) In-Reply-To: (Kenichi Handa's message of "Wed, 27 Feb 2008 16:28:02 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-NAI-Spam-Score: -2.5 X-NAI-Spam-Rules: 2 Rules triggered BAYES_00=-2.5, HAS_X_HELO=0 X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:90628 gmane.emacs.pretest.bugs:21314 Archived-At: >> > C-s =C3 =B6 =C3 =B6 =C3 =B6 C-g C-g C-g C-g ESC x r e p o TAB r >> Hmm... "=C3 =B6" in latin-1 is "0xC3 0xB6" which is the utf-8 codes for = =F6, >> so the C-h l output indicates your terminal sends utf-8 sequences and >> Emacs gets them fine, but if you say that instead of =F6 you saw some = =B6, >> it may indicate that your keyboard-coding-system somehow is set to use >> latin-1 coding system rather than utf-8, or maybe the binary codes get >> treated as latin-1 by the unicode-charset. > It seems that something is broken in isearch-x.el (although > unicode merge didn't change it). I'm now investigating. Thanks. > But, perhaps, it's time to implement the decoding of > keyboard input by C. After multi-tty merge, we have the > function tty_read_avail_input. I think that is the right > place to do that decoding. Now that we've moved the keyboard decoding to input-event-map, I'm not sure what would be the benefit. Of course, if we can just reuse C code and get rid of the encoded-kbd code, that's good. Stefan