From: Andy K. <and...@gm...> - 2010-09-17 12:12:26
|
On 17 September 2010 12:38, Earnie wrote: > Andy Koppe wrote: >> On 16 September 2010 13:07, Earnie wrote: >>> I am reviewing the patches msysgit made to MSYS and will be in >>> discussion with that group of developers on why some of the changes were >>> made. Some are just intuitive and will go in without much problem. One >>> change will affect RXVT because it gets rid of tty >> >> Can you elaborate on that one? (I assume mintty would be affected too.) >> > > http://repo.or.cz/w/msysgit.git/blob/msys:/src/rt/patches/0006-Ignore-the-tty-option-from-the-CYGWIN-environment-va.patch "There is no working pty emulation in MSys, so it makes no sense to allow asking for that emulation. The symptoms are non-working vi, looping ssh questions to accept host keys or passwords." That's quite wrong. MSYS's pty emulation works fine. Rxvt and mintty both use it. (It's a lot slower than Cygwin's latest, but that's another matter.) Rxvt and mintty don't actually care about CYGWIN=tty though, because the setting only affects MSYS programs invoked in a console window, where it enables the pipe-based pty emulation instead of connecting the standard streams directly to the console window. As far as I can see, that's working fine too, e.g. it enables suspending of processes with ^Z, and MSYS vim and ssh look perfectly happy with it. I guess what the comment is referring to is running non-MSYS programs in a pty session. As Chuck and I know only too well, interactive console programs often don't work properly when they're talking to the pair of pipes that the pty emulation is based on instead of being connected directly to a console device. Andy |