X-Recipient: archive-cygwin AT delorie DOT com
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:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=mLOPY84Uc3UHfSQ0
	LLhIrcPxfEbjrpxilMZznic9m5Rl/k//+54DA68TG+KU+gafRJWkk3kKStxoruyY
	H2jk4/vk9i3aF5ehCu/TZr9n6U3mBuTrLAdWNaOMLjmD0akk5SgxakamlG51ZKE+
	90M0/7YifMShwM4Sasbca1lg1bw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=PA/qXPp050+7/nEcWPQ5Lz
	MgUF8=; b=Wc5NilY0RAuY3mFMBYdQ+18syq+zduCZfHusG4EwptNLdaJuIRBYr3
	fOHFxS1ZiSJjLXVcDmy9buFnWtXAekleH2XBhaR1Xihilq2iZTW3O6FwUNPSRrnd
	dLkpzleP+9TRGCv2LyIyzDM5vWPkrFqfoa641+f2j957f1ucHm9xQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00,FOREIGN_BODY,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=wurde, States, United, united
X-HELO: mout.kundenserver.de
Subject: Re: xterm / Windows 10 question
To: cygwin AT cygwin DOT com
References: <CAJuLzxBtLCYDs6tm3Q7+0imQqX+SgGd3=8aKJsGcU7Ling2mYw AT mail DOT gmail DOT com> <CAJuLzxD7n_C+mPCA0tAAnevHCKuXCpYDVTRx+_Rej8cu8=rDxw AT mail DOT gmail DOT com> <3ba87eb1-538f-d527-7448-59eba13e11b5 AT gmail DOT com>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <2635a311-4114-72a8-7424-64f19258fd81@towo.net>
Date: Tue, 5 Jun 2018 08:21:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <3ba87eb1-538f-d527-7448-59eba13e11b5@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Note-from-DJ: This may be spam


Am 05.06.2018 um 06:03 schrieb Marco Atzeri:
>
>>
>> On Mon, Jun 4, 2018 at 5:47 PM, Matt Nicholas <mattdn AT gmail DOT com> wrote:
>>
>>> ...
>>>
>>> I start Cygwin/X as follows:
>>>
>>> (1) open a Cygwin64 Terminal window
>>> (2) cd /usr/bin
>>> (3) ./xinit -- -multiwindow &
>>>
>>> That works as expected, and creates an initial xterm window. I can then
>>> start multiple independent xterm windows.
>>>
>>> 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.
>>> Typing the character twice, causes the character to appear, but things
>>> don't work as expected.
>>> For example, a command like:
>>>       find . -name "*.exe"
>>> fails to find any files even though there are ".exe" files to be found.
>>>
>>> I've seen various suggestions online stating that I need to change the
>>> setting under 'Control Panel, Languages' so that the selected 
>>> language is
>>> "English (United States)", rather than "English (International)".
>>> I did that and it did not solve the problem (nor make any discernible
>>> difference).
>>>
>>> A few other clues:
>>>       (1) The problem does not occur in a Cygwin64 Terminal window.
>>>       (2) I set things up the same way on a Windows 7 PC that I also 
>>> use,
>>> and do not experience this problem in xterm windows.
>
> It seems that Xterm, and I assume the all X server,
> is using a different Keyboard layout than Mintty.
> One with dead-keys.
Mintty supports dead keys too, per Windows keyboard layout, and also a 
compose key.
Double-quote, however, should not be a dead key, in typical keyboard 
layouts. What X keyboard layout do you have?
Is it really a double-quote you finally have on the command line? Did 
you check that with `od`?

>
> The best explanation I found on keyboard with dead-keys is
> https://zauner.nllk.net/post/0014-windows-no-dead-keys/
>
> For changing setting for the X system, some guidance is available on:
> https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
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