Web lists-archives.com

Re: xterm / Windows 10 question




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 <dbcygwin@xxxxxxxxx>
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