Re: xterm / Windows 10 question

[Matt Nicholas <mattdn at gmail dot com>]

Sorry, I left out the word "not" in my last message.
I meant to say:

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

Apologies for the omission.
--- Matt



On Mon, Jun 4, 2018 at 5:47 PM, Matt Nicholas <mattdn@gmail.com> wrote:

> Hello,
>
> I have a question that I hope someone may be able to help me with.
>
> 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.
>
> 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 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.
>
> So... now I'm confused.  If this were entirely a Windows 10 issue I would
> not expect a Cygwin64 Terminal window to behave differently from an xterm
> window.
> On the other hand, it this were entirely an issue with Cygwin/X and xterm
> windows, I would not expect Windows 10 and Windows 7 to be different.
>
> (I verified that this is not an issue with the xterm version.  I have
> version 327 on the Win7 PC, and 330 on the Win10 PC, but I tried 327 on the
> Win10 PC and it made no difference.)
>
> Anyone have any ideas about how to resolve this?
>
> Thanks
> --- Matt
>
> MattDN@gmail.com
>
>
>
>
>
>

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