From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Next pretest Date: Tue, 26 Jan 2010 19:27:09 +0100 Message-ID: References: <87fx5vef1j.fsf@stupidchicken.com> <87sk9sga2k.fsf@stupidchicken.com> <83aaw068mj.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1264530625 11176 80.91.229.12 (26 Jan 2010 18:30:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 26 Jan 2010 18:30:25 +0000 (UTC) Cc: cyd@stupidchicken.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 26 19:30:17 2010 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 1NZqA7-0007bM-Qc for ged-emacs-devel@m.gmane.org; Tue, 26 Jan 2010 19:29:16 +0100 Original-Received: from localhost ([127.0.0.1]:57473 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZqA8-0006XI-K6 for ged-emacs-devel@m.gmane.org; Tue, 26 Jan 2010 13:29:16 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZqA1-0006SP-Pw for emacs-devel@gnu.org; Tue, 26 Jan 2010 13:29:09 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZq9x-0006Hu-J3 for emacs-devel@gnu.org; Tue, 26 Jan 2010 13:29:09 -0500 Original-Received: from [199.232.76.173] (port=42217 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZq9x-0006Hh-EJ for emacs-devel@gnu.org; Tue, 26 Jan 2010 13:29:05 -0500 Original-Received: from mail-bw0-f215.google.com ([209.85.218.215]:42655) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZq9u-000330-VP; Tue, 26 Jan 2010 13:29:04 -0500 Original-Received: by mail-bw0-f215.google.com with SMTP id 7so1699822bwz.26 for ; Tue, 26 Jan 2010 10:29:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ozB9XztUQg3IaeO6+JRdJt24ywtPjfO/92Ra6yxpkVw=; b=JTCHXpySrQ8ZkQ1Djm91m+vmN/h2cSGTtU2nwzwKyzP53EZyI1aO0rQ9opQizc8DkF E9clE3USAC8P9sueP7BVeASwWqc1w0FU0tSFXYSyj0COM3hTCQHYMTjkOYGLeCKjtcvK 8OJACD6z3yT5MvXtuS8eQ63UYcVhfEIzuDp48= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=SpqX0f19J6VrowNcRGJwH+qlINd2dlHuuhJ1sWfnJft0nUWOI9kKZscS9f3sztojLD yfkUXEE3rf3ZyB5PQ/ErR8ECfr5hhyut+tgvnoQv9fCueLZHh/R3Uz0Is1PW6Tih692L b0zDcUBdAbmtqd1cROfYGrZT+yKvRdKZZFyWc= Original-Received: by 10.204.8.220 with SMTP id i28mr1791894bki.143.1264530542354; Tue, 26 Jan 2010 10:29:02 -0800 (PST) In-Reply-To: <83aaw068mj.fsf@gnu.org> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:120459 Archived-At: On Tue, Jan 26, 2010 at 19:09, Eli Zaretskii wrote: > Probably not, since it triggers an assertion. True, but sometimes assertions grow stale, and nobody notices for a long time because apparently not many developers build with assertions enabled. > Does this happen with 12XX codepages as well? C:\> chcp 1252 C:\> emacs -Q -nw =C3=B1 produces the same effect. > This is a non-optimized build, I presume, right? =C2=A0We aren't chasing > wild geese here, right? "--with-gcc (4.4) --no-opt --cflags -DENABLE_CHECKING=3D1 -DXASSERTS=3D1 -IC:/emacs/build/include -fno-crossjumping" I'm using the Twilight Dragon Media MinGW build, but I'm reasonably sure it happened too with stock MinGW gcc 3.X, so it's not likely a compiler bug. > Can you see what event is received w32term.c:w32_read_socket in this > case? =C2=A0Is that function at all called in the -nw session? =C2=A0If n= ot, try > w32inevt.c:key_event. =C2=A0In the latter, it would be interesting to see > what was event->wVirtualKeyCode (around line 426). I cannot debug this right now, but I'll try tonight. > Also, how did you type these non-ASCII characters on your keyboard? > Do you have keys for them, or do you need to use AltGr or some such? They have their own keys (I'm using a Spanish keyboard). But AltGr-4 + n (which produces =C3=B1) triggers the assertion too. Juanma