DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=XZ6e6ZXt4bYfTPl7d8d5BzZvO5Eje
	kmOk1HXS5WYADnw3Ak14Hoh4CljTdmh2lZ0MZcFE74DArou7jnZC69ZrNt0Cr/Qi
	fWjppEbsvnxWke+3Osri9dyPC9/c/+EVSPFUUlqAvnezTbSmHG5VPEgfd7E8yTUp
	J/QYIG8OG2saBo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: Matt Nicholas <mattdn@gmail.com>
Date: Mon, 4 Jun 2018 17:47:33 -0700
Message-ID: <CAJuLzxBtLCYDs6tm3Q7+0imQqX+SgGd3=8aKJsGcU7Ling2mYw@mail.gmail.com>
Subject: xterm / Windows 10 question
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

Hello,

I have a question that I hope someone may be able to help me with.

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.

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

So... now I'm confused.  If this were entirely a Windows 10 issue I would
not expect a Cygwin64 Terminal window to behave differently from an xterm
window.
On the other hand, it this were entirely an issue with Cygwin/X and xterm
windows, I would not expect Windows 10 and Windows 7 to be different.

(I verified that this is not an issue with the xterm version.  I have
version 327 on the Win7 PC, and 330 on the Win10 PC, but I tried 327 on the
Win10 PC and it made no difference.)

Anyone have any ideas about how to resolve this?

Thanks
--- Matt

MattDN@gmail.com

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