X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=T1D3Q9Xi0O+HkJdi
	y29l39OfFvLNBTKdYnZ0mDqFxrbkDek2bpl2ATWenm4GsUWdR+c/yZ7vM0N7oCuC
	zt+Z/uABL4s9ZJ3E8DoRNXoBpr9hmSAE7rk9QwmReNCuc4Lq4UwZmDhroUaGOe0h
	IVW5DKkvXYWhJ50XVLMGjxpLNAQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=RWiD7MT7Vx28KXIaZ4G081
	jIKPs=; b=Oa01SwuBldnEVM7zbUTMSYEtKjrke7C924MsZcEsqnvjlzqDZux0VV
	oflBQCspG4sZY1reLriDRmyWs9Ygrf8u3r3vcK0PNrYLY1NySapqoHAgisMjPVWV
	moSSC14NefmPCYgyPGJS+RXYXv4gA9trZHg/3k4X6ihkaUd9Mc+z8=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=mateosian, Mateosian, ruby, Youve
X-HELO: mail-io0-f170.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:subject:to:references:from:reply-to:message-id         :date:user-agent:mime-version:in-reply-to:content-language         :content-transfer-encoding;        bh=gBLDRnMKt4ptKlG4CobbXIbObosnj8kRUB2dLHzcfAc=;        b=HwDKa5cBYCq+og3E+zVe2XNuro5dSLFUUGRqzJ8YD7E1FcC56mBEI/Q8TxeWvhY5RF         PfWkjO8XXISlxpWjMy5qv7QgjuZg9PcEzyAt4sWmOmRbj23Db0j+HG+AEFWZ4iVdys3t         6aBt9vVMzuigeEqzzQU1bBjcS1s8RFsVlryjRl/+I8tGEKlA3jK/neeTRcsrsLOve4hc         YU9/7Wfg9aSpiKxssHJUofaPu8Nvd7d6wFhA9fJ+u/dkwhh9Td/pq4I8tU8lQq9VWSdY         OytFazXcXwDC7keQW8VTzq/jJGctbiQWRQM6Ixw/h9KTui3fkq7YLBXjJBf0ET2rGz0D         rUzA==
X-Gm-Message-State: AJaThX7pQFIUJ9BfJngDIe4lgFaKvkAHxC5YZrLvMFZjAHQFRHanC3Yq	I4gW2ZwkxlZXZjNp9Qo8WxN/4Q==
X-Google-Smtp-Source: AGs4zMY1ZSjNTCO+erwYYHhZhbNPCFhQjc/55+YCL+wuSmM7tMHPrgas395LMRhdiCxVq0999NbYNA==
X-Received: by 10.107.183.20 with SMTP id h20mr16101827iof.23.1512185462265;        Fri, 01 Dec 2017 19:31:02 -0800 (PST)
Subject: Re: Requested report
To: cygwin AT cygwin DOT com
References: <CAD1QJjXeJxQMS2-mZbF1F8YcKEOa=oa3OtNcEsvTwgEJf9duiw AT mail DOT gmail DOT com> <CAD1QJjWfq4oihUHQVddyv-rw-r=YpFmk0y_uLKHWAR6+gtpw_Q AT mail DOT gmail DOT com> <621196364 DOT 20171130223717 AT yandex DOT ru> <CAD1QJjXFsYLDtiWHz=1pNdLs7j43fjcx4MkFt9fdrgAijH+vXw AT mail DOT gmail DOT com> <f4868991-0b26-f80f-805f-eb875b1aa602 AT gmail DOT com> <18DA4DAE-F801-45B9-9E3D-F03BF7420D07 AT solidrocksystems DOT com>
From: cyg Simple <cygsimple AT gmail DOT com>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <f40cef08-3d92-8aa5-f75e-1a6bd22bea7e@gmail.com>
Date: Fri, 1 Dec 2017 22:31:01 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <18DA4DAE-F801-45B9-9E3D-F03BF7420D07@solidrocksystems.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

On 12/1/2017 10:35 AM, Vince Rice wrote:
>> On Dec 1, 2017, at 8:55 AM, cyg Simple wrote:
>>
>> On 11/30/2017 11:41 PM, Richard Mateosian wrote:
>>> Thanks. I wasn't actually using Cygwin, but Ruby apparently does so under
>>> the covers. Or maybe my path leads it astray, because I used to use Cygwin
>>> -- a long time ago.   ...RM
>>>
>>
>> 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.
> 
> 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 processor; I have a mintty session open, but only use it when I need to do shell-related things.
> 

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.

> There's no reason not to have Cygwin in the Windows path, and lots of reasons to do so (grep, cat, tail, head, etc., etc.).
> 

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.

-- 
cyg Simple

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