From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Brian.Inglis@SystematicSw.ab.ca, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: [ANNOUNCEMENT] xterm 348-1
Date: Thu, 07 Nov 2019 02:40:00 -0000 [thread overview]
Message-ID: <20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp> (raw)
In-Reply-To: <e8821312-8750-48a1-e7f2-d7ce34f7d431@SystematicSw.ab.ca>
On Wed, 6 Nov 2019 10:24:29 -0700
Brian Inglis wrote:
> Does tcsh input work properly under mintty instead of xterm?
Yes, it works under mintty.
> How does it work in cat, od, etc.? That can not include using input via tcsh?
cat, od, etc. are works even if they are started from tcsh.
> Presumably you are using IME(s) for Japanese input - which at what input layer(s)?
I'm using Microsoft-made IME (MS-IME).
> I noticed that xterm was updated to Unicode 10 then 11, with changes to CJK/East
> Asian character properties and handling; tcsh dropped libcatgets1 as a
> dependency; those could affect input.
I confirmed the issue does not occur in the combination of:
Debian/sid + xterm 349 + tcsh 6.21.00
Debian/buster + xterm 344 + tcsh 6.20.00
Therefore, this may be a cygwin dedicated issue.
Wait. I have just found /etc/X11/app-defaults/XTerm has a entry
*VT100*eightBitInput: false
which is added from cygwin xterm 348-1.
Removing this line or changing the value to true solves this issue.
Katsumi, could you please check if this solves the issue?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
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:[~2019-11-07 2:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 22:43 Yaakov Selkowitz
2019-11-01 1:36 ` Katsumi Yamaoka
2019-11-06 12:13 ` Takashi Yano
2019-11-06 14:11 ` Brian Inglis
2019-11-06 15:48 ` Takashi Yano
2019-11-06 17:24 ` Brian Inglis
2019-11-07 2:40 ` Takashi Yano [this message]
2019-11-07 8:31 ` Thomas Wolff
2019-11-07 10:16 ` Takashi Yano
2019-11-07 15:52 ` Brian Inglis
2019-11-07 15:50 ` Brian Inglis
2019-11-07 17:03 ` Brian Inglis
2019-11-08 4:19 ` Katsumi Yamaoka
2019-11-08 13:13 ` Brian Inglis
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=20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=yamaoka@jpl.org \
/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).