Mail Archives: cygwin/2011/03/31/14:24:05
X-Recipient: | archive-cygwin AT delorie DOT com
|
X-SWARE-Spam-Status: | No, hits=-1.3 required=5.0 tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
|
X-Spam-Check-By: | sourceware.org
|
MIME-Version: | 1.0
|
In-Reply-To: | <00c101cbefcb$f3b38860$db1a9920$@com>
|
References: | <00c101cbefcb$f3b38860$db1a9920$@com>
|
Date: | Thu, 31 Mar 2011 20:23:51 +0200
|
Message-ID: | <AANLkTine1m5A1A_ur7GTwuLJ9q==Kx0o4Hbvpc02wEA3@mail.gmail.com>
|
Subject: | Re: Preferred path setup for cygwin
|
From: | Csaba Raduly <rcsaba AT gmail DOT com>
|
To: | cygwin AT cygwin DOT com
|
Cc: | Gary Furash <furashgary AT gmail DOT com>
|
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm
|
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
|
Hi Gary,
On Thu, Mar 31, 2011 at 7:49 PM, Gary Furash wrote:
> For cygwin to work best, should your $PATH be something like:
>
> =A0 =A0 =A0 =A0[STANDARD WINDOWS PATH]:[CYGWIN PATHS (e.g., usr/bin])
>
> Along with some aliases that ensure that cygwin uses the CYGWIN rather th=
an
> the WINDOWS versions of same named programs (e.g., "find")
>
> OR
>
> =A0 =A0 =A0 =A0[CYGWIN PATHS]:[STANDARD WINDOWS PATHS]
If you want to use Cygwin, it's probably best to keep the Cygwin paths
at the front. The Cygwin installer sets up Bash to do this
automagically: the Windows PATH is imported and transformed into POSIX
path by cygwin.dll (this happens for every Cygwin program), then
/etc/profile prepends the necessary directories ( /usr/local/bin,
/usr/bin, /bin ) to $PATH. Other shells might do similar things.
IMO, the problem with aliases is that they create an illusion, which
can lead to surprises if a Windows program with the same name as a
Cygwin program ever appears in the Windows search path.
At my workplace, we have such occasional surprises caused by ClearCase
and its hostinfo program, which every now and then gets executed by a
configure script (Cygwin does not have hostinfo, so the effect is the
same as if the ClearCase program directory was ahead of Cygwin's).
It is possible to add the Cygwin directories to the Windows path, for
easy access to grep & other tools from a Windows prompt. Adding them
to the beginning would hide the Windows version of find; I don't
consider this a loss :)
Hope this helps,
Csaba
--=20
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torv=
alds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
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
- Raw text -