From: Matt Nicholas <mattdn@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: xterm / Windows 10 question
Date: Wed, 13 Jun 2018 21:22:00 -0000 [thread overview]
Message-ID: <CAJuLzxAH__+ogjRz1LG4JE3Ar50OQ2goeHPYAvmPwoKwhZ0wHA@mail.gmail.com> (raw)
In-Reply-To: <371735234.20180613055129@yandex.ru>
Hi Andrey,
I'm starting to feel a bit guilty about wasting bandwidth on the Cygwin
mailing list because
my initial question was answered by other posters and the problem has, as a
practical matter,
been solved.
That's not to say I understand all aspects of the interaction between
Windows 10 keyboard layouts,
the X Server, and xterm windows.
To answer your questions:
> Why? Do you need the INTL one? If not, just remove it.
Yes, I agree. I did remove ENG INTL following Microsoft's documented
procedure.
(Settings > Time & Language > Region & Language, select ENG INTL, click
Remove.)
This appeared to work -- ENG INTL no longer shows up in the Region &
Language dialog.
However, it remains one of the choices I can toggle through using <Windows
Key>+space.
So... presumably I don''t yet know how to actually remove it.
> That makes little sense to me.
> What if I have more than one input language? What if I actually NEED
both
> layouts?
Yes, of course, if you need more than one input language you should keep
them installed.
What I was trying to say in my previous post was simply that the X Server
uses the layout that's in effect
when you start the X Server. So if, for example, you want xterm windows to
start up with "ENG US"
rather than "ENG INTL", then you should select "ENG US" before starting the
X Server.
If you fail to do that, it seems you can switch after the fact using
"setxkbmap".
Best Regards,
--- Matt
On Tue, Jun 12, 2018 at 7:51 PM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> Greetings, Matt Nicholas!
>
> > Hi Jon,
>
> > Thanks for the additional comments.
>
> > The two keyboard layouts that are installed are "ENG US" and "ENG INTL".
> > (These are the two I see when I toggle through them using <Windows
> > Key>+space.)
>
> Why? Do you need the INTL one? If not, just remove it.
>
> > I just rebooted the laptop and did not observe the problem with xterm
> > windows that prompted my initial post. I suppose this all makes sense
> > based on the fact that xterm windows use the layout that was in effect
> when
> > the X Server was started. I.e., you can't subsequently change the
> behavior
> > of xterm by selecting a different layout using <Windows Key>+space. (At
> > that point can use "setxkbmap us".)
>
> > My understanding at this point is that the only thing necessary is to
> make
> > sure the desired layout (in my case "ENG US") is selected before starting
> > the X Server.
>
> That makes little sense to me.
> What if I have more than one input language? What if I actually NEED both
> layouts?
>
>
> --
> With best regards,
> Andrey Repin
> Wednesday, June 13, 2018 5:50:14
>
> 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
prev parent reply other threads:[~2018-06-13 18:37 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
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 [this message]
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=CAJuLzxAH__+ogjRz1LG4JE3Ar50OQ2goeHPYAvmPwoKwhZ0wHA@mail.gmail.com \
--to=mattdn@gmail.com \
--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).