> I'm still surprised that mc works fine for you guys. > Does your /usr/bin/mc.exe come from MSYS2 (just making sure)?
Yes. Look at the attachments I previously sent. > Also, can you check your `TERM` environment > variable and output of `chcp`? From a windows 7 "command prompt": D:\msys64\usr\bin>chcp Active code page: 437 D:\msys64\usr\bin>printenv | grep TERM TERM=cygwin I have no idea why TERM is set to cygwin. It's not something I remember intentionally setting. However, it seems likely that TERM=cygwin has something to do with mc.exe working correctly in "command prompt" here. So I did an experiment. In windows 7 "command prompt", I ran "set TERM=ansi-nt" and tried running MSYS2 mc.exe program. It started, in black and white instead of color, but was mostly unresponsive, no cursor keys worked, at least ^O worked, and ^D allowed me to exit. Next, I ran "set TERM=cygwin" to revert, and things worked perfectly next time I ran mc.exe program. > Do you have Ansicon, Clink, Cmder, ConEmu or > anything similar installed and enabled? No. I do have cygwin installed, never use it. > I don't think winpty is supposed to be configurable. So it seems. All I know is winpty does NOT work correctly in this instance, as I previously explained. From mintty / winpty combination, the pdcurses program starts, but the cursor keys do not work. Daniel ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
