xterm / Windows 10 question
Sun Jun 10 20:52:00 GMT 2018
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
> [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
> 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?
Volunteer Cygwin/X X Server maintainer
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin