Hi Jon, 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)*. 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.) Best Regards, --- Matt On Wed, Jun 6, 2018 at 1:17 PM, Jon Turney <jon.tur...@dronecode.org.uk> wrote: > 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 <dbcyg...@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
