Message-ID: <4BBE1B8E.2030405@cornell.edu>
Date: Thu, 08 Apr 2010 14:08:14 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: On TMP, TEMP... variables
References: <4BBE0C53.9030905@alice.it>
In-Reply-To: <4BBE0C53.9030905@alice.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 4/8/2010 1:03 PM, Angelo Graziosi wrote:
> I remember that there was some discussion on December[*] regarding these
> environment variables. The conclusion was, if I remember correctly, that
> Cygwin, by default, *does not set* them, like GNU/Linux systems.
>
> Indeed my Windows installation sets them but Cygwin shows that they *are
> not*:
>
> $ echo $TEMP
>
> $ echo $TMP
>
> $ echo $TMPDIR
>
> Now in http://cygwin.com/cygwin-ug-net/setup-env.html I read:
>
> "In addition to PATH, HOME, and LD_LIBRARY_PATH, there are three other
> environment variables which, if they exist in the Windows environment,
> are converted to UNIX format: TMPDIR, TMP, and TEMP[...] If set, these
> variables will be used by some Cygwin applications, possibly with
> unexpected results."
>
> These words seem to contradict the above statement. So, how is the 'matter'?

Cygwin doesn't set them, it just converts them to UNIX format if they're 
already set.  But then, as the documentation goes on to say, the default 
~/.bashrc unsets them.  So I don't think there's any contradiction.

Ken

--
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