DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=B1fIALQscHVPJ1mf
	Q5ohvybPI1V/OcliSYq5/FvadMpLj1PRJgA5NGmLojSbK2MA/4+U2MMndUwA7gkC
	Ob78dsLG3uTo28rVk72KJ0oXqG0F8hul+ZMRxDqpezhywyuFsKQz1OAyEL0z+ChE
	I+gYfZGW+cA4VNKHzHI7jX1zRzQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: xterm / Windows 10 question
To: The Cygwin Mailing List <cygwin@cygwin.com>
References: <CAJuLzxBtLCYDs6tm3Q7+0imQqX+SgGd3=8aKJsGcU7Ling2mYw@mail.gmail.com> <0f87d9a8-4e32-4edb-26b4-648b28358309@gmail.com> <CAJuLzxDpFHjo_bMnnSBd2qbeK9iTx54Y=p85u3Quwegt4Y8A8w@mail.gmail.com>
Cc: Matt Nicholas <mattdn@gmail.com>
Reply-To: The Cygwin Mailing List <cygwin@cygwin.com>
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <636f4ac0-bd18-5ba0-5b81-c67f6d8fea96@dronecode.org.uk>
Date: Wed, 6 Jun 2018 21:17:52 +0100
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: <CAJuLzxDpFHjo_bMnnSBd2qbeK9iTx54Y=p85u3Quwegt4Y8A8w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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 <dbcygwin@gmail.com>
> 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  <Windows Key>+<space>.  Many Dell machines are
>> configured to use the US-international keyboard that encodes "<char> 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