From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 65935 invoked by alias); 2 Dec 2017 05:07:24 -0000 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 Received: (qmail 65918 invoked by uid 89); 2 Dec 2017 05:07:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_50,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=mateosian, Mateosian, ruby, Youve X-HELO: outbound-ss-1812.hostmonster.com Received: from gproxy1-pub.mail.unifiedlayer.com (HELO outbound-ss-1812.hostmonster.com) (69.89.25.95) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 02 Dec 2017 05:07:22 +0000 Received: from cmgw4 (cmgw5 [10.0.90.85]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id DABA9175C0E for ; Fri, 1 Dec 2017 22:07:20 -0700 (MST) Received: from box867.bluehost.com ([69.195.124.67]) by cmgw4 with id gt7H1w00N1TMts501t7LTc; Fri, 01 Dec 2017 22:07:20 -0700 X-Authority-Analysis: v=2.2 cv=JNNLi4Cb c=1 sm=1 tr=0 a=x/h8IXy5FZdipniTS+KQtQ==:117 a=x/h8IXy5FZdipniTS+KQtQ==:17 a=IkcTkHD0fZMA:10 a=ocR9PWop10UA:10 a=9HtPj3WGZ7ZNkTY1zEUA:9 a=QEXdDO2ut3YA:10 Received: from 99-106-192-34.lightspeed.ftwotx.sbcglobal.net ([99.106.192.34]:57548 helo=[192.168.1.89]) by box867.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eL01F-0022kU-3y for cygwin@cygwin.com; Fri, 01 Dec 2017 22:07:17 -0700 From: Vince Rice Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Requested report Date: Sat, 02 Dec 2017 05:07:00 -0000 References: <621196364.20171130223717@yandex.ru> <18DA4DAE-F801-45B9-9E3D-F03BF7420D07@solidrocksystems.com> To: cygwin@cygwin.com In-Reply-To: Message-Id: <9563066C-2379-4369-AEDC-21A2CCBD9DDA@solidrocksystems.com> X-BWhitelist: no X-Exim-ID: 1eL01F-0022kU-3y X-Source-Sender: 99-106-192-34.lightspeed.ftwotx.sbcglobal.net ([192.168.1.89]) [99.106.192.34]:57548 X-Source-Auth: vrice@solidrocksystems.com X-Email-Count: 1 X-Source-Cap: c29saWRycjI7c29saWRycjI7Ym94ODY3LmJsdWVob3N0LmNvbQ== X-Local-Domain: yes X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00015.txt.bz2 > On Dec 1, 2017, at 9:31 PM, cyg Simple wrote: >=20 > On 12/1/2017 10:35 AM, Vince Rice wrote: >>> On Dec 1, 2017, at 8:55 AM, cyg Simple wrote: >>>=20 >>> On 11/30/2017 11:41 PM, Richard Mateosian wrote: >>>> Thanks. I wasn't actually using Cygwin, but Ruby apparently does so un= der >>>> the covers. Or maybe my path leads it astray, because I used to use Cy= gwin >>>> -- a long time ago. ...RM >>>>=20 >>>=20 >>> You should not put Cygwin in your Windows PATH environment at the system >>> level or user levels. If you need it during a command shell session, >>> add it after you start the command shell. I've never heard that Ruby >>> intentionally uses Cygwin. >>=20 >> What? I've had cygwin in my path since the B19 days (that's right, even = *before* the infamous B20). >> I regularly (and almost exclusively) use cygwin tools in the command pro= cessor; I have a mintty >> session open, but only use it when I need to do shell-related things. >>=20 >=20 > So? You've just been lucky to not have had an issue. Adding Cygwin to > the Windows PATH has been ill advised since the B19 days. Other tools > are bound to distribute Cygwin and interfere with what you have > installed. It happens all the time. Not putting Cygwin's path directly > in the Windows PATH helps resolve some of the issues caused by multiple > installs of Cygwin. However, it doesn't eliminate all of the issue. No, I haven=E2=80=99t been =E2=80=9Clucky=E2=80=9D and no, nothing is =E2= =80=9Cbound to=E2=80=9D. I=E2=80=99ve never installed a single tool that distributes cygwin. >> There's no reason not to have Cygwin in the Windows path, and lots of re= asons to do so >> (grep, cat, tail, head, etc., etc.). >=20 > There's lots of reasons to not do so as I've mentioned above. Yes, it's > nice to have these in a Windows command session. You could start a > command window via a .bat file whose purpose is to set PATH before > starting cmd.exe. This keeps other tools from seeing it. You didn=E2=80=99t mention =E2=80=9Clots of reasons=E2=80=9D. You mentioned= one reason =E2=80=94 multiple installs of cygwin. And you admitted that not having cygwin in the path doesn=E2=80=99t even so= lve all of the problems that might arise from that issue. If you have multiple cygwin installations, then solve that problem. There= =E2=80=99s no reason to punish yourself for something that *might* happen (and which has no reason to happ= en). And, as I mentioned (with examples), there *are* lots of reasons TO put it in your pa= th. So, again, there is nothing wrong with having cygwin in the Windows path. I= t is silly to install cygwin and then not be able to use the tools in day-to-day life in the comm= and processor. -- 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