Greetings, Corinna Vinschen! >> >>>>> Not specific to this snapshot but it happens when trying to test it: >> >>>>> If a cygwin console is started from a cygwin terminal (e.g. in mintty: >> >>>>> cygstart /Cygwin.bat), the TERM variable is set incorrectly. >> >>>>> Suggested fix: ... unset TERM to Cygwin.bat. >> >>>> unset would be better (more neutral) choice in a long-term, IMO. >> >>> Actually, unset doesn't exist in cmd (blush). >> >>> It should be "set TERM=" then. >> >> However you spell it :) >> >> Using same assignment in shell would have nearly equal results. >> > Having something like case `tty` in /dev/cons*) TERM=cygwin;; esac in >> > /etc/profile would be a clumsy workaround and possibly have tricky >> > glitches. >> >> Except not every shell read /etc/profile >> >> > My proposal catches the issue at its root in the simplest way. >> > I would provide a patch (if needed) if I had an idea in which package >> > Cygwin.bat is hiding;-) >> >> It's autogenerated.
> ...by setup itself. Changing this would require to create a new setup. > Is it worth it? It's not a priority, but something that needs fix. > I mean, how often do people start Cygwin.bat from > mintty? I never occured to me to do that at all :} > And if so, why not just call it like this: > $ TERM=cygwin cygstart /Cygwin.bat For that, you need to know, that you need to do it this way. -- WBR, Andrey Repin (anrdae...@yandex.ru) 21.02.2014, <16:15> 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
