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:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=g5p2OGhm6/2t6bbl SJNkjow3QA4sLkFCefYcsosP0x9XkKuFxSpsAdd7v/tjbZX4hGJk4IMIUWJvoZID ZXyin+qs4u10ZKVCbwpgM9seaLs7Y7/L7eCxgrtkztpZrLODsKH1IpMmNFMuSjvd dmEnjZnqWFI04TJ2fCBZ37I6WXY= 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:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=default; bh=jRQdpJaB5lkqaVOyTlDw8+ G9m5Q=; b=Mt54Wt4iEDAd/xakRxA3H5eFwQuG5hmdKSCgB77MGyqqn5T7r4OMTj 8AxBScQvnh01zm32i0vw7pdgiJfIIdszL+3hgam6Pk/9BGGJWss91Wro3tbvOpkq 4tHxEKxu5pPdCe0W5EYkBgWrUsS6uiv17jlpfOMfxp/wi8ZnISDA8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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: Yes, score=5.1 required=5.0 tests=AWL,BAYES_95,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=H*UA:Bat!, H*x:Bat!, H*r:4.80.1, H*r:sk:postmas X-HELO: smtp.ht-systems.ru Date: Wed, 30 Mar 2016 05:49:04 +0300 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <918411307.20160330054904@yandex.ru> To: All Subject: Re: Unable to start mintty. In-Reply-To: <819064387.20160330052747@yandex.ru> References: <819064387 DOT 20160330052747 AT yandex DOT ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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. -- With best regards, Andrey Repin Wednesday, March 30, 2016 05:42:49 Sorry for my terrible english... -- 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