Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: dragon.dn.rsc.raytheon.com: agrimm owned process doing -bs Date: Thu, 9 Oct 2003 11:21:56 -0600 (MDT) From: Andrew Grimm X-X-Sender: agrimm AT dragon To: cygwin AT cygwin DOT com Subject: Re: problem with tcsh-6.12.00-7.tar.bz2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII >> This package includes /etc/csh.login which has the line: >> >> set TERM=cygwin >> >> This should instead read: >> >> set term=cygwin >> >> which will set the shell variable term and the environment variable >> TERM correctly when tcsh is used as the base shell for the Cygwin shell >> window. > > Thanks for the heads up. I'll patch this for the next tcsh release. > > Actually it shouldn't matter. $term is set correctly when starting > tcsh from a command line window nevertheless. The above `set' command > should never get called since Cygwin sets the TERM environment variable > to "cygwin" automatically, if $TERM isn't found in the environment. > > Corinna It appears to be the other if-condition (tty=conin) that is causing that line to run when I bring up the Cygwin shell window. In truth I hadn't seen this problem until recently. This broke for me because I had to install Rational Rose. Believe it or not, this product sets TERM=nutc in your global Windows environment. While I personally find this a poor implementation on Rational's part, I am stuck with that if I want the Rational suite of development products to work. That variable affects Cygwin tcsh, so the /etc/csh.login change really does help me. Thanks, Andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/