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
