From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50661 invoked by alias); 5 Jun 2018 00:51:54 -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 49249 invoked by uid 89); 5 Jun 2018 00:51:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=States, United, united, H*c:alternative X-HELO: mail-wm0-f44.google.com Received: from mail-wm0-f44.google.com (HELO mail-wm0-f44.google.com) (74.125.82.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Jun 2018 00:51:51 +0000 Received: by mail-wm0-f44.google.com with SMTP id r15-v6so1596272wmc.1 for ; Mon, 04 Jun 2018 17:51:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=bAQy3Y9ljlqaCmQ9NE9noip2n4l78VtPWAt9b2wuQ6E=; b=U9Xc4ZkQlfyxENouciLlAPU5ljKPwoIkoWWZiUGFulCyZYh2K+iquGSEMqAXscSXh5 vaXDFGpGcmjrJ/D2F9WlROdIEDQvv2rUAX2xzAL/xAA3N1TfchG9KiUQytWX6h3g8BLv XsglzrRnkWpENV8uMmJsPNKN6DvpBXaqfytU6dQnCiXuMhvBwlV9cKSkaRqmFR/kBUJ3 nL7sjFRYwsKB/XzxaBf5qEeNJc1PLWqdY4gn1PUi4hTUsynXsEhr7zTDC5xzjXKsCuQJ K5CMtcKO6x0FefbXHC1lsSX6v3G0yRYmoTY6K9K/Qfmp2HOk78zbEyYGv5dpWUHPzMZZ hwmg== X-Gm-Message-State: ALKqPwezIr2+PbsOyXN/BjY5Un0lmpVvd+5YY9sEcwqB20ml9sItPy98 5zz0NBdJHvOT2g/MhnXJQCpNdeXtD6SilJjJ61qTBYG6 X-Google-Smtp-Source: ADUXVKKLYt3Wk9UFIYBl/Xipg8omiFDVD2fwH35hNmYK4Gr2y5Ya6zVAfkDX3vZ+PNiL1Y9JNT0w696ZbSf1+zH/0+4= X-Received: by 2002:a50:9442:: with SMTP id q2-v6mr26330939eda.70.1528159909301; Mon, 04 Jun 2018 17:51:49 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:b102:0:0:0:0:0 with HTTP; Mon, 4 Jun 2018 17:51:48 -0700 (PDT) In-Reply-To: References: From: Matt Nicholas Date: Tue, 05 Jun 2018 00:51:00 -0000 Message-ID: Subject: Re: xterm / Windows 10 question To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-06/txt/msg00028.txt.bz2 Sorry, I left out the word "not" in my last message. I meant to say: 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). Apologies for the omission. --- Matt On Mon, Jun 4, 2018 at 5:47 PM, Matt Nicholas wrote: > 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