X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4991EDD7.4090804@bmts.com>
Date: Tue, 10 Feb 2009 16:12:55 -0500
From: Ralph Hempel <rhempel AT bmts DOT com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: RFE?: CygWinDir in ENV? (was Re: How does one find where Cygwin    was  installed from Windows?)
References: <4990B031 DOT 4050807 AT tlinx DOT org> <4990B128 DOT 7030004 AT cygwin DOT com>  <4990CB8D DOT 3050704 AT tlinx DOT org> <4990D05A DOT 4050202 AT cygwin DOT com> <4990DA52 DOT 9050900 AT tlinx DOT org>  <4990E0BF DOT 1010502 AT cygwin DOT com> <4990EC89 DOT 8070901 AT tlinx DOT org> <4991004F DOT 1080006 AT cygwin DOT com>  <4991E1CC DOT 9060804 AT tlinx DOT org> <Pine DOT NEB DOT 4 DOT 64 DOT 0902101450530 DOT 21431 AT panix1 DOT panix DOT com> <4991EB3C DOT 3090800 AT cygwin DOT com>
In-Reply-To: <4991EB3C.3090800@cygwin.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-brucetelecom.com-MailScanner-Information: Please contact Bruce Telecom 519.368.2000 for more information
X-brucetelecom.com-MailScanner: Found to be clean
X-brucetelecom.com-MailScanner-From: rhempel AT bmts DOT com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Larry Hall (Cygwin) wrote:

> This can be done now, if you look back through the thread to all the
> different options I outlined and even a few scripts others have thrown
> in.  What Linda is proposing here is simply having the mechanism for
> communicating this be an environment variable.  While this could arguably
> make it easier to do what you want, it doesn't mean that you can't do
> it now for either Cygwin 1.5 or the upcoming 1.7 (though you may be
> required to do something different for 1.5 and 1.7.)

For what it's worth, you can easily retrieve a known registry
key (that you have permission to access) using a batch file
and then store that in a temporary variable. (I'm sure the gurus
already know this)

I really dislike software that pollutes my environment for me, but
I really like software that lets me do it myself, if that makes any
sense.

Ralph



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