From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8508 invoked by alias); 6 Jun 2018 20:18:05 -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 8361 invoked by uid 89); 6 Jun 2018 20:17:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-7.3 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=aussie, Hx-languages-length:1804, Aussie, United X-HELO: out1-smtp.messagingengine.com Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 06 Jun 2018 20:17:58 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 94BCF21DFD; Wed, 6 Jun 2018 16:17:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 06 Jun 2018 16:17:55 -0400 X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.102] (host31-51-207-186.range31-51.btcentralplus.com [31.51.207.186]) by mail.messagingengine.com (Postfix) with ESMTPA id ED75C10294; Wed, 6 Jun 2018 16:17:54 -0400 (EDT) Subject: Re: xterm / Windows 10 question To: The Cygwin Mailing List References: <0f87d9a8-4e32-4edb-26b4-648b28358309@gmail.com> Cc: Matt Nicholas Reply-To: The Cygwin Mailing List From: Jon Turney Message-ID: <636f4ac0-bd18-5ba0-5b81-c67f6d8fea96@dronecode.org.uk> Date: Wed, 06 Jun 2018 20:18:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2018-06/txt/msg00074.txt.bz2 On 05/06/2018 18:19, Matt Nicholas wrote: > Hi David, > Thanks for the suggestion. Unfortunately, toggling the input method does > not make a difference in an xterm window. (It does, by the way, have the > effect you mention in a Cygwin64 terminal window.) The X server does not use the Windows input method, but tries to setup an appropriate X keyboard configuration based on the Windows keyboard layout selected when it starts up. I suspect that an unexpected keyboard configuration is being used, if it has dead keys when you don't want them. Can you show /var/log/XWin.0.log, or at least the portion of that describing what keyboard configuration is being selected, e.g.: > [1236607.031] (--) Windows keyboard layout: "00000809" (00000809) "United Kingdom", type 4 > [1236607.031] (--) Found matching XKB configuration "English (United Kingdom)" > [1236607.031] (--) Model = "pc105" Layout = "gb" Variant = "none" Options = "none" > --- Matt > > > On Mon, Jun 4, 2018 at 7:21 PM, David Billinghurst > wrote: > >> On 2018-06-05 10:47, Matt Nicholas wrote: >> >> I recently obtained a Dell Precision laptop running Windows 10. >>> I installed 64-bit Cygwin, including various packages that are not part of >>> the minimal install. >>> >> >> The problem I'm having is that when I type single quote or double quote >>> characters in the xterm window, no character appears with the first >>> keystroke. >>> >> This may be an issue with the input method configured for the keyboard. >> You can toggle this with +. Many Dell machines are >> configured to use the US-international keyboard that encodes " to an >> umlaut, so "e to ë and so on. As a monlingual Aussie I find the plain "US >> Keyboard" has fewer surprises. -- 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