This is the mail archive of the
mailing list for the Cygwin project.
Re: xterm / Windows 10 question
- From: Matt Nicholas <mattdn at gmail dot com>
- To: David Billinghurst <dbcygwin at gmail dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 5 Jun 2018 10:19:44 -0700
- Subject: Re: xterm / Windows 10 question
- References: <CAJuLzxBtLCYDs6tm3Q7+0imQqX+SgGd3=8aKJsGcU7Ling2mYw@mail.gmail.com> <email@example.com>
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.)
On Mon, Jun 4, 2018 at 7:21 PM, David Billinghurst <firstname.lastname@example.org>
> 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
> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple