From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12206 invoked by alias); 8 Nov 2019 13:13:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 12195 invoked by uid 89); 8 Nov 2019 13:13:29 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=asian, Asian, japanese, Japanese X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.137) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 08 Nov 2019 13:13:28 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id T44qiyRH617ZDT44ri5Mm0; Fri, 08 Nov 2019 06:13:26 -0700 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: [ANNOUNCEMENT] xterm 348-1 To: cygwin@cygwin.com References: <20191106211318.263462ceb47f01f6fd63c64e@nifty.ne.jp> <420cec84-46a7-c55c-f723-dfd96d39d39b@SystematicSw.ab.ca> <20191107004841.33764763bbb1ba364347c46c@nifty.ne.jp> <20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <2e5a851b-43d7-bb5b-33b7-560215cf85c0@SystematicSw.ab.ca> Date: Fri, 08 Nov 2019 13:13:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: <20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00044.txt.bz2 On 2019-11-06 19:39, Takashi Yano wrote: > 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? Excellent catch! Great work! -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- 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