public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Unable to start mintty.
Date: Sun, 03 Apr 2016 22:08:00 -0000	[thread overview]
Message-ID: <57019447.704@towo.net> (raw)
In-Reply-To: <56FB7FFB.4030609@towo.net>

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

      reply	other threads:[~2016-04-03 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  2:35 Andrey Repin
2016-03-30  2:50 ` Andrey Repin
2016-03-30  7:28   ` Thomas Wolff
2016-04-03 22:08     ` Thomas Wolff [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57019447.704@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).