From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96530 invoked by alias); 12 Jun 2018 02:01:52 -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 96438 invoked by uid 89); 12 Jun 2018 02:01:51 -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=HX-Received:a50, H*r:a50, laptop, eng X-HELO: mail-wm0-f42.google.com Received: from mail-wm0-f42.google.com (HELO mail-wm0-f42.google.com) (74.125.82.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 12 Jun 2018 02:01:49 +0000 Received: by mail-wm0-f42.google.com with SMTP id e16-v6so17765889wmd.0 for ; Mon, 11 Jun 2018 19:01:49 -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=81okEV/V03srR1nCblW1coLRkiKfhzuCr0QfVpPwz0o=; b=q1AsaHxu61rNv4EJl1qnH9LxcB8meDCd3kWYuyIlV9Fz8Cha/XNoqy7Xjzlh81OFsC vYD2uEpjzpNACP9ug8IdJfAZK8X5eBEcP2aAe2DuB8n76ADwejRx1hKGO4+QhbytiYH5 BvCJZKJgyYxUPzpTkRCVmf6/i8gpPrIKsJiR/83gAOvuILdfVH/ACXE4a+4jVQo4wcc/ 9YoUcxmYJOhu0S4cEZWqjJ+fqAJXXqSPYjfN7Jh3yqeAbTycXTuGcRs92mefEMHIoj4M +kzIMxW0tS9DU7HGBxTguGTFZrsfFrsubT02XFE0UhrHdQHAltmnMXekVM0+qYFhZa4p Dm7g== X-Gm-Message-State: APt69E3vwWvlqmFaH+cpfbD2v2tW9GfDwFDLO7siFauV5NhXQ7fyn97K ofyUTxeJIRSDz8/tgt7eDajfcZ32tCpC0c2J1rXvEQ2u X-Google-Smtp-Source: ADUXVKJaumMwsUBk+9BBoFr6n4966v7g0WL8Bs2xm7pGvwv3x/tgMWJZsqwUhmWBOKrba4T67tbwegm99bbL98U6XJo= X-Received: by 2002:a50:ad07:: with SMTP id y7-v6mr1561938edc.78.1528768907598; Mon, 11 Jun 2018 19:01:47 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:b102:0:0:0:0:0 with HTTP; Mon, 11 Jun 2018 19:01:46 -0700 (PDT) In-Reply-To: <058ccbd0-ecc4-87db-85c4-1447e28d589e@dronecode.org.uk> References: <0f87d9a8-4e32-4edb-26b4-648b28358309@gmail.com> <636f4ac0-bd18-5ba0-5b81-c67f6d8fea96@dronecode.org.uk> <058ccbd0-ecc4-87db-85c4-1447e28d589e@dronecode.org.uk> From: Matt Nicholas Date: Tue, 12 Jun 2018 08:53:00 -0000 Message-ID: Subject: Re: xterm / Windows 10 question To: The Cygwin Mailing List Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-06/txt/msg00119.txt.bz2 Hi Jon, Thanks for the additional comments. The two keyboard layouts that are installed are "ENG US" and "ENG INTL". (These are the two I see when I toggle through them using +space.) I just rebooted the laptop and did not observe the problem with xterm windows that prompted my initial post. I suppose this all makes sense based on the fact that xterm windows use the layout that was in effect when the X Server was started. I.e., you can't subsequently change the behavior of xterm by selecting a different layout using +space. (At that point can use "setxkbmap us".) My understanding at this point is that the only thing necessary is to make sure the desired layout (in my case "ENG US") is selected before starting the X Server. --- Matt On Sun, Jun 10, 2018 at 1:52 PM, Jon Turney wrote: > On 06/06/2018 23:33, Matt Nicholas wrote: > >> That was the clue I needed. Thanks! >> >> Here are the relevant lines from my */var/log/xwin/XWin.0.log*: >> >> [494293.296] (--) Windows keyboard layout: "00020409" (00020409) "United >> States-International", type 7 >> [494293.296] (--) Found matching XKB configuration "English >> (USA,International)" >> [494293.296] (--) Model = "pc105" Layout = "us_intl" Variant = "none" >> Options = "none" >> [494293.296] Rules = "base" Model = "pc105" Layout = "us_intl" Variant = >> "none" Options = "none" >> >> I'm not sure why the X server starts with *Layout = "us_intl"*, because if >> I look in *Control Panel > All Control Panel Items > Language* it says the >> language is *English (United States)*. >> > > "Display language" and "Keyboard Layout/Input method" are different > concepts, although they seem to be somewhat combined in the settings app > now. > > However, I found that if I enter the command "*setxkbmap us*" in an xterm >> window it solves the problem (i.e., single quote and double quote >> characters are no longer dead keys). >> >> I'm still not sure how best to configure it so that the X server starts >> with "us" instead of "us_intl" automatically, but that's a minor issue in >> any case -- entering the "setxkbmap us" command is easy enough. >> (I can probably put the "setxkbmap us" command in ".bash_profile", if I >> don't find a more appropriate place.) >> > > I don't think this is working as intended. If you don't have the US > international keyboard layout active when the X server is started (which > I'm assuming isn't the case, or you wouldn't be surprised by the deadkeys > that layout uses), it shouldn't be selected. > > Perhaps you can clarify what keyboard layouts you have installed? > > -- > Jon Turney > Volunteer Cygwin/X X Server maintainer > -- 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