From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Matt Nicholas <mattdn@gmail.com>
Subject: Re: xterm / Windows 10 question
Date: Wed, 06 Jun 2018 20:18:00 -0000 [thread overview]
Message-ID: <636f4ac0-bd18-5ba0-5b81-c67f6d8fea96@dronecode.org.uk> (raw)
In-Reply-To: <CAJuLzxDpFHjo_bMnnSBd2qbeK9iTx54Y=p85u3Quwegt4Y8A8w@mail.gmail.com>
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@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
next prev parent reply other threads:[~2018-06-06 20:18 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
2018-06-05 2:21 ` David Billinghurst
2018-06-05 17:19 ` Matt Nicholas
2018-06-06 20:18 ` Jon Turney [this message]
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=636f4ac0-bd18-5ba0-5b81-c67f6d8fea96@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=mattdn@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).