public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Marco Atzeri <marco.atzeri@gmail.com>, cygwin@cygwin.com
Subject: Re: xterm / Windows 10 question
Date: Tue, 05 Jun 2018 15:35:00 -0000	[thread overview]
Message-ID: <381414776.20180605183102@yandex.ru> (raw)
In-Reply-To: <3ba87eb1-538f-d527-7448-59eba13e11b5@gmail.com>

Greetings, Marco Atzeri!

> It seems that Xterm, and I assume the all X server,
> is using a different Keyboard layout than Mintty.
> One with dead-keys.

Thanks for the hint, this is not limited to X server only, but plagues other
remote control systems under win10 as well (RManSys, TeamViewer) and even USA
keyboard is affected.
I had to phone back my customers and ask them to enter things by themselves
since I was completely unable to type anything meaningful due to wild
differences between keyboard layouts. And I know for a fact that their
keyboards are no different than mine. (In fact, I've held each device in my
own hands at least once, and haven't had a problem typing anything locally.)

> The best explanation I found on keyboard with dead-keys is
> https://zauner.nllk.net/post/0014-windows-no-dead-keys/

Explanation, yes, but it does not help even a little, since Windows silently
activate keyboard layouts by application request.
I've been fighting this issue since XP and only solution I've found was to
change registry keys to force Windows to think that your custom layout is the
standard one.
You don't need to change keyboard signatures, or replace DLL's, which should
theoretically make it possible to exercise in Win10 as well.
The relevant registry key is
HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\<language ID>

> For changing setting for the X system, some guidance is available on:
> https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg


-- 
With best regards,
Andrey Repin
Tuesday, June 5, 2018 18:17:43

Sorry for my terrible english...


--
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

  parent reply	other threads:[~2018-06-05 15:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  0:47 Matt Nicholas
2018-06-05  0:51 ` Matt Nicholas
2018-06-05  4:04   ` Marco Atzeri
2018-06-05  6:21     ` Thomas Wolff
2018-06-05 15:35     ` Andrey Repin [this message]
2018-06-05  2:21 ` David Billinghurst
2018-06-05 17:19   ` Matt Nicholas
2018-06-06 20:18     ` Jon Turney
2018-06-06 22:33       ` Matt Nicholas
2018-06-06 22:46         ` Stefan Baur
2018-06-10 20:52         ` Jon Turney
2018-06-12  8:53           ` Matt Nicholas
2018-06-13  8:10             ` Andrey Repin
2018-06-13 21:22               ` Matt Nicholas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=381414776.20180605183102@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).