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=pgNz9dwKwAT5E5SD
	iOAGQ9XHHhr7JRN9ZQNojfxoTeWdREtD8yLK0beMw9oB0WxQ6YqOrOcOiChzsVCZ
	H7dgGIdq/HC2h5CHp8uHnhU9xHH8m2qEkAonz+irAO2PNwn95CSc388xZsB/3hIJ
	+ZQW86lVwZJYS0fvhL3X2XvUw3Q=
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=4f/PJtNmjNBwsfERBMUmiY
	GztWE=; b=iZBcuw4IeZ1kkIG5WTA7poC8P81iSq3Il5FDHfo1p/kTCf6bIcRtOQ
	WLTCHfPA6sqVlRQ7heKroDsEXazw3GOBnbYdINIY2y8dIVAHLVpzWMiKob7g14GN
	gVaTwHmH7e/NenOpqMe5UL09DZzb3kjActjco3FXxdYsICc7FN65I=
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=1.1 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=UD:UTF-8, frustrating, ru_RU.UTF-8, ru_RUUTF8
X-HELO:	mout.kundenserver.de
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>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<56FB7FFB.4030609@towo.net>
Date:	Wed, 30 Mar 2016 09:27:55 +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:	<918411307.20160330054904@yandex.ru>
X-UI-Out-Filterresults:	notjunk:1;V01:K0:Dnzy7IZMIF8=:3VrdqFoFbWSsWW/IhQy4On eefYMfWLDiq+9dRexdsmR5XwvGmBpsQYgnSqp8ibQQcuO0RpOZqvzREMHrzieD33RPSwUoahm CVIace8bP3bHFlXfyu1BFSwZHg//TSFmxs7SoKhRmsoOWVVuFajwvxbKmAJEUEEgDzwD+8+fz s/fBRL2yNO5bx+fnR6NGQgBFimR0bYSdohiPT31KWPBFbtT+VcgTfilLDjajssnZBEIOk9GtQ kxOYm9InLB6BBhuxSEg955b7tVExCMSF7jEUJ0PYWHjR2wU9jN92P84zvkaNwWVA8i4DmJI5P dAF+SFzHxxfa1LDMXUmBFlKOAaeWUI5osuriyJTaQENP+a6hhjbvbhHHuT2i2V/O5/12JErMT v/pAC43KeibSsYp2KVkMrYETP3186SQoWvf5INdq5Rmvtib6f7yUzlqDH2hXffukIpfwmr+zF +PBrdxFnjYyQWEHZVqQ0xngFrEpGSC+uHglVeMHsaKlb4OPk3jF57yCZZW8UTyRvqEo/1QpC4 M7FrEiNU+dOUAXEtaVgX0C1BuuJNqdpnLpCwKI9Z/yyY1EYim3/O2BnASLywYyOgawJazIV2M yAwAtX3kk399pNffUbVNj2XdfaJFjy9J/RkB65HcwKc6jKGOcPygatAN3Wp0QV9YT5LTSnG3l Cwr7L0Y+mvNEZFGOv8l1rx3dTkeEwQXU7nQ5TXqx9c+W2crfiVbLFifFfen2/X8QFqIvlNVR6 vUMm6PdDXWUfcZ2+
X-IsSubscribed:	yes

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.
It doesn't seem to happen with option -d, by the way.
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

- Raw text -