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=vhMNlk7Px1BropCj
	KrOzub8zQg21bTYWqBoFii9F0HInZk8HPx619kpYOR8yYItIV9mrbt0DS8XiSL5u
	hTBzl+kMs6Fy3V923IO1a/KgKV/21kWn/gEeQg8ZmRgfiKs65FzzWD72L5nYiPVC
	5ppKBoL3/HUq4Yr4c7HmWEdXmu4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: Unable to start mintty.
To: cygwin AT cygwin DOT com
References: <819064387 DOT 20160330052747 AT yandex DOT ru> <918411307 DOT 20160330054904 AT yandex DOT ru> <56FB7FFB DOT 4030609 AT towo DOT net>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <57019447.704@towo.net>
Date: Mon, 4 Apr 2016 00:08:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <56FB7FFB.4030609@towo.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Am 30.03.2016 um 9:27 schrieb Thomas Wolff:
> Am 30.03.2016 um 4:49 schrieb Andrey Repin:
>> Greetings, All!
>>
>>> I've not used mintty for quite some time, and discovered today that 
>>> I no
>>> longer able to start it inside a directory. Quite frustrating moment 
>>> is that I
>>> can perfectly start it from desktop shortcut, but not from console.
>>> After much fiddling, largely out of desperation, I tried to set 
>>> LANG= in
>>> console to the same value it have in GUI. Much to my surprise, 
>>> mintty readily
>>> popped up, like it wasn't a few long hours of constant failure.
>>> The short version:
>>> LANG=ru_RU.CP866  - mintty close immediately.
>>> LANG=ru_RU.UTF-8  - mintty start just fine.
>> Another useful bit of info: I've had locale/encoding forced to 
>> ru_RU/UTF-8 in
>> mintty settings. Was working fine in the past, overriding the locale set
>> through environment variables (which let me had different locale 
>> setting in
>> console, and still fully utilize unicode capabilities of mintty 
>> started from
>> it).
>>
>> I've made two small tweaks to the way I invoke mintty now:
>> 1. I've removed enforced locale in application settings and
>> 2. I've corrected environment in the wrapper calling mintty from 
>> console,
>> but this is not really a desirable solution.
> Yes, this has been reported to 
> https://github.com/mintty/mintty/issues/530 already, and it seems the 
> small change of 2.3.3 isn't actually causing the problem but may have 
> revealed another lurking bug which I'm currently chasing.
I hope 2.3.4 (just uploaded) gets rid of this problem.
However, I suspect some subtle infrastructure bug (gcc or cygwin) behind 
it, see my mail of today "crash caused by stack-allocated array in child 
process after fork?" (https://cygwin.com/ml/cygwin/2016-04/msg00041.html).
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