public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: xterm / Windows 10 question
Date: Tue, 05 Jun 2018 06:21:00 -0000	[thread overview]
Message-ID: <2635a311-4114-72a8-7424-64f19258fd81@towo.net> (raw)
In-Reply-To: <3ba87eb1-538f-d527-7448-59eba13e11b5@gmail.com>


Am 05.06.2018 um 06:03 schrieb Marco Atzeri:
>
>>
>> On Mon, Jun 4, 2018 at 5:47 PM, Matt Nicholas <mattdn@gmail.com> wrote:
>>
>>> ...
>>>
>>> I start Cygwin/X as follows:
>>>
>>> (1) open a Cygwin64 Terminal window
>>> (2) cd /usr/bin
>>> (3) ./xinit -- -multiwindow &
>>>
>>> That works as expected, and creates an initial xterm window. I can then
>>> start multiple independent xterm windows.
>>>
>>> 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.
>>> Typing the character twice, causes the character to appear, but things
>>> don't work as expected.
>>> For example, a command like:
>>>       find . -name "*.exe"
>>> fails to find any files even though there are ".exe" files to be found.
>>>
>>> I've seen various suggestions online stating that I need to change the
>>> setting under 'Control Panel, Languages' so that the selected 
>>> language is
>>> "English (United States)", rather than "English (International)".
>>> I did that and it did not solve the problem (nor make any discernible
>>> difference).
>>>
>>> A few other clues:
>>>       (1) The problem does not occur in a Cygwin64 Terminal window.
>>>       (2) I set things up the same way on a Windows 7 PC that I also 
>>> use,
>>> and do not experience this problem in xterm windows.
>
> It seems that Xterm, and I assume the all X server,
> is using a different Keyboard layout than Mintty.
> One with dead-keys.
Mintty supports dead keys too, per Windows keyboard layout, and also a 
compose key.
Double-quote, however, should not be a dead key, in typical keyboard 
layouts. What X keyboard layout do you have?
Is it really a double-quote you finally have on the command line? Did 
you check that with `od`?

>
> The best explanation I found on keyboard with dead-keys is
> https://zauner.nllk.net/post/0014-windows-no-dead-keys/
>
> For changing setting for the X system, some guidance is available on:
> https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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

  reply	other threads:[~2018-06-05  6:21 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 [this message]
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
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=2635a311-4114-72a8-7424-64f19258fd81@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.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).