X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=IFSfpSft3S2xmWeB
	3EKmXnZClKkR4ygdMa3WkSznE9/ie2RPV4tN25nptCoKwvdb3MGjQMDGuPF7yJUR
	3U9R2mPtZF6sQlrXHxEkNBIbGKCjxCsdd8EQPFBN9Q1tML7oBH03oF//AQ0CSKKA
	zpg3jv/hHAHaUGCtGuKjwa3s92U=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=Wip8AH92ipQ5K6G2jOCodw
	LYNyk=; b=REaQWT9fwryQGAsyX7eI1oGDFKgijkvEiSX83f6vR0zN/3LeHJKHF3
	EXAuATNZWk/FdMIkJUP5c5H8su190KMwWK3YeQNVLipBZfHyA3hTP1NgqTYBQ4RN
	+YaDt9gozPmD2wk/FK2Rhw3Q3y2HMqUaR8WNC0NiJXLgxPZGqUCvU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=ham version=3.3.2 spammy=adress, one, Hx-spam-relays-external:sk:mrelaye, H*RU:sk:mrelaye
X-HELO: mout.kundenserver.de
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.8-3
To: cygwin AT cygwin DOT com
References: <20170131131616 DOT GC29504 AT calimero DOT vinschen DOT de> <40c92f1e987a9162742766816abb4a03 AT smtp-cloud2 DOT xs4all DOT net> <20170131153245 DOT GA8905 AT calimero DOT vinschen DOT de> <09c7b42a-7b8d-52b7-ce18-4e681eb51f05 AT towo DOT net> <20170214084537 DOT GD25846 AT calimero DOT vinschen DOT de> <09253e2d-af27-ddca-2b49-b65460440f69 AT towo DOT net> <6488d88d-f6b8-674d-692c-8372977a4707 AT redhat DOT com> <0da58793-0b76-1f13-aca3-06ed6aa83dc3 AT towo DOT net> <4bc220da-11d0-fd39-4691-27c6ec9cbbb8 AT towo DOT net> <59ecea04-2e3c-41af-9f4a-93a9b772a9e4 AT towo DOT net> <20170216124949 DOT GF3889 AT calimero DOT vinschen DOT de>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <bb2239bd-8cc3-2992-1554-18a04736ace7@towo.net>
Date: Thu, 16 Feb 2017 21:32:29 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170216124949.GF3889@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-UI-Out-Filterresults: notjunk:1;V01:K0:KG+5BzXuONI=:3bi1UXSiPqBFhwzPPR6cUz 7O2RzCd7CMq8msitYcV/FFmbTVcLN+XTYQnP2wu1bKx4Ey/e+xKohm3FCyvPdm5fqyc8E6Z1r 6PFm3RsNWkn29g/gf4Y4sf+itHOwnIXUUG0w8Q2C+n1loU/hIZpPBQHgoi6HnLu/QLeXOb5lK A7NSInOQwesIEm+olX5jg2pWvxPtrF5Q/1S8AFxXdkeImfjcQauVqb7S4jq3lYD7f1GoVmURX h0yGw6YYhMcBJ1Txt4caHD1cBSRqKbkh24WQuIos5ppce2vD8JOulIc1K75ARycc3Mrt2lM4L QMP2L84KXbxFZgqGrTzVfZ9Z3B6XbAvC3ky5YLguYS8N07oobv0kun7JZoaHcOZzgmyEre1fy vfkpVQ1w6CFbVj2IN3vN4ZzHIoKINBgrHUPWCCWuXFWw8VCTuO0GsF1krsCRhR2HbHDpXiV3f YtuavUCoplF/4YUFv7JQQrtz3yFevFop2zRewbET1ADJde/AUXxkfuCEGvi52jOZjYCWJZXZd yQBoQmPiEk3kGTBqTihrIAiUbyNPbA5XHLc9PGbaT5wibQapEV3vrh1kMX8mYgLZH50lnqKPn qjJmwoeX7Fkqn0/idwHdTB0Q7p0OAn4ApTZ0FZwCHwC7AaE1D2XDOwcvr63Qnfjp/IFI+dY2C IwP6lVqsjU8ZYID/uEpz6wLB+pfG9N5+Ry5oeFD3ooCPHgayinvtT+hfiojpVWFUO/edT0e9i qWoIAm0soLehO7/5
X-IsSubscribed: yes

Am 16.02.2017 um 13:49 schrieb Corinna Vinschen:
> On Feb 15 23:19, Thomas Wolff wrote:
>> Am 14.02.2017 um 21:35 schrieb Thomas Wolff:
>>> Am 14.02.2017 um 21:29 schrieb Thomas Wolff:
>>>> Am 14.02.2017 um 20:56 schrieb Eric Blake:
>>>>> On 02/14/2017 01:40 PM, Thomas Wolff wrote:
>>>>>>> No.  We're talking about a function in the master side
>>>>>>> of the tty, while
>>>>>>> the applications started in the terminal are on the slave side.
>>>>>> I am not familiar with the concept of setting termios properties on
>>>>>> either the master or slave side of a pty. I've only ever set
>>>>>> them in the
>>>>>> client application, including my tests about IUTF8 which worked. Would
>>>>>> setting on the master side imply it's set for the clients implicitly,
>>>>>> and can it be changed later, e.g. when mintty character encoding is
>>>>>> being changed from the Options dialog?
>>>>>> And you say the function of erasing characters on BS is in the master
>>>>>> side? To be honest, this confuses me. I thought it's a
>>>>>> client function,
>>>>>> like readline() would perform if used (apparently not by
>>>>>> dash), which is
>>>>>> kind of an enhanced version of the tty cooked mode and used
>>>>>> to work even
>>>>>> without the new flag, right?
>>>>> The readline source code does not mention IUTF8; and neither bash nor
>>>>> dash need to reference it, because if the tty handling code sets it
>>>>> correctly for what the terminal is going to display, then the clients
>>>>> that are read()ing from the tty never even see BS in cooked mode (the
>>>>> master side of the terminal handles BS before the read() completes in
>>>>> the slave, if I'm understanding it correctly).
>>>> This does not comply with my (limited) understanding of pty stuff.
>>>> In mintty, forkpty will create a master/slave pty; mintty feeds it
>>>> on the master side, while the client program (usually a shell) reads
>>>> from the slave side. Mintty never handles BS for input, it simply
>>>> feeds it into the pty. "Line disciplines" like cooked mode must be
>>>> handled on the slave side.
>>> Also, I've tried both options in mintty. Setting the flag on the master
>>> side has weird effects, initially blocking the terminal process.
>>> Setting it on the slave side works fine.
>> That was a mistake (got something wrong when testing). It works from either
>> side alike.
>> I've now patched mintty to keep the flag in sync with the character
>> encoding, including on later changes (from Options menu or by escape
>> sequence).
> There's an ESC sequence to change the codeset?  Do you mean the
> alternate codeset sequence \e[10m / \e[11m
Oh, that one! Thanks for mentioning, I had overlooked it and fixed 
mintty now to consider it.
> or is there something more sophisticated?
I actually meant to adress 
https://github.com/mintty/mintty/wiki/CtrlSeqs#locale and there is also 
\e%G and \e%@.

I just notice that later changing of the IUTF8 flag from the master side 
does not seem to work on a Window 10 system (although it works 
initially) while it does work on a Windows 7 system. Weird.

------
Thomas

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