X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.1 required=5.0	tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject: Re: How to make persistent changes to PATH in cygwin?
Date: Wed, 02 Jan 2013 12:01:50 -0800
Lines: 17
Message-ID: <kc23nc$ga4$2@ger.gmane.org>
References: <BLU0-SMTP361C219C76F9B12A644D34CE220 AT phx DOT gbl> <50E47DEC DOT 9030702 AT cs DOT umass DOT edu> <BLU0-SMTP47819E18FC14AEFDE24B972CE220 AT phx DOT gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
In-Reply-To: <BLU0-SMTP47819E18FC14AEFDE24B972CE220@phx.gbl>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 1/2/2013 10:45 AM, Aaron Schneider wrote:
> On 02/01/2013 19:35, Eliot Moss wrote:
>> Every time you open up mintty you are starting a new login bash.
>> The way to set environment variables "persistently" (your term,
>> not mine) is to add the export command to your .bash_profile or
>> similar bash file read by bash when it starts up.  This is not
>> specific to cygwin, but is normal Unix-like behavior.
>
> I've workarounded it adding the desired path to windows' path 
> directly, which is imported into cygwin each time mintty is started.
>
That's not really a good solution. Take a moment to read the bash(1) man 
page and familiarize yourself with it's startup capabilities. Take 
control of your own environment.
-- 
Andrew DeFaria <http://defaria.com>
This space for rent


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