Am 20.02.2014 02:26, schrieb Andrey Repin:
Greetings, Thomas Wolff!
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.
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;-)
------
Thomas
---
Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz
ist aktiv.
http://www.avast.com
--
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
