From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9628 invoked by alias); 31 Mar 2011 18:23:58 -0000 Received: (qmail 9618 invoked by uid 22791); 31 Mar 2011 18:23:57 -0000 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 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 31 Mar 2011 18:23:52 +0000 Received: by iyi20 with SMTP id 20so3491668iyi.2 for ; Thu, 31 Mar 2011 11:23:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.142.133 with SMTP id s5mr3815918icu.64.1301595831815; Thu, 31 Mar 2011 11:23:51 -0700 (PDT) Received: by 10.231.184.81 with HTTP; Thu, 31 Mar 2011 11:23:51 -0700 (PDT) In-Reply-To: <00c101cbefcb$f3b38860$db1a9920$@com> References: <00c101cbefcb$f3b38860$db1a9920$@com> Date: Thu, 31 Mar 2011 19:54:00 -0000 Message-ID: Subject: Re: Preferred path setup for cygwin From: Csaba Raduly To: cygwin@cygwin.com Cc: Gary Furash Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-03/txt/msg00860.txt.bz2 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