From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55609 invoked by alias); 5 Jun 2018 15:35:11 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 53065 invoked by uid 89); 5 Jun 2018 15:35:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=UD:ru, HX-Priority:Normal, SYSTEM, H*F:D*yandex.ru X-HELO: forward101j.mail.yandex.net Received: from forward101j.mail.yandex.net (HELO forward101j.mail.yandex.net) (5.45.198.241) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Jun 2018 15:35:07 +0000 Received: from mxback15g.mail.yandex.net (mxback15g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:94]) by forward101j.mail.yandex.net (Yandex) with ESMTP id 0C8031242652; Tue, 5 Jun 2018 18:35:04 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback15g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id kQngYQQRH3-Z3Giucjr; Tue, 05 Jun 2018 18:35:04 +0300 Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id GM1UEheceJ-Z3OCKOAV; Tue, 05 Jun 2018 18:35:03 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Tue, 05 Jun 2018 15:31:02 -0000 Date: Tue, 05 Jun 2018 15:35:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <381414776.20180605183102@yandex.ru> To: Marco Atzeri , cygwin@cygwin.com Subject: Re: xterm / Windows 10 question In-Reply-To: <3ba87eb1-538f-d527-7448-59eba13e11b5@gmail.com> References: <3ba87eb1-538f-d527-7448-59eba13e11b5@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00037.txt.bz2 Greetings, Marco Atzeri! > It seems that Xterm, and I assume the all X server, > is using a different Keyboard layout than Mintty. > One with dead-keys. Thanks for the hint, this is not limited to X server only, but plagues other remote control systems under win10 as well (RManSys, TeamViewer) and even USA keyboard is affected. I had to phone back my customers and ask them to enter things by themselves since I was completely unable to type anything meaningful due to wild differences between keyboard layouts. And I know for a fact that their keyboards are no different than mine. (In fact, I've held each device in my own hands at least once, and haven't had a problem typing anything locally.) > The best explanation I found on keyboard with dead-keys is > https://zauner.nllk.net/post/0014-windows-no-dead-keys/ Explanation, yes, but it does not help even a little, since Windows silently activate keyboard layouts by application request. I've been fighting this issue since XP and only solution I've found was to change registry keys to force Windows to think that your custom layout is the standard one. You don't need to change keyboard signatures, or replace DLL's, which should theoretically make it possible to exercise in Win10 as well. The relevant registry key is HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\ > For changing setting for the X system, some guidance is available on: > https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg -- With best regards, Andrey Repin Tuesday, June 5, 2018 18:17:43 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple