Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: cygwin/clearcase problem Date: Wed, 8 Aug 2001 12:09:26 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: cygwin/clearcase problem Thread-Index: AcEgIyiLbXNEnfHLR+ChdD8zVYiWdQAAPzWA From: "Andrew Goldstein" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA23894 Actually we seem to not have it imported. using echo $TMP produces no output. env and set commands do not contain TMP, but do contain TEMP. Andrew -----Original Message----- From: Christopher Faylor [mailto:cgf AT redhat DOT com] Sent: Wednesday, August 08, 2001 11:58 AM To: cygwin AT cygwin DOT com Subject: Re: cygwin/clearcase problem On Wed, Aug 08, 2001 at 11:47:18AM -0400, Richard Ramos wrote: >I found the problem. > >In the windows (2000) environment, I have 2 separate temp environment >variables (TMP and TEMP). For some reason, only TEMP was >imported into bash. My script used TEMP. Apparently, clearcase uses TMP. > >I was assuming all of the windows environment variables were imported into >bash. All windows environment variables are imported by cygwin. TMP, however, is special in that the path is translated from windows format to UNIX format, e.g. if TMP is set to c:\tmp, cygwin translates it to /cygdrive/c/tmp . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/