This is the mail archive of the
mailing list for the Cygwin project.
Re: Requested report
- From: Vince Rice <vrice at solidrocksystems dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 1 Dec 2017 09:35:25 -0600
- Subject: Re: Requested report
- Authentication-results: sourceware.org; auth=none
- References: <CAD1QJjXeJxQMS2-mZbF1F8YcKEOa=oa3OtNcEsvTwgEJf9duiw@mail.gmail.com> <CAD1QJjWfq4oihUHQVddyv-rw-r=YpFmk0y_uLKHWAR6+gtpw_Q@mail.gmail.com> <firstname.lastname@example.org> <CAD1QJjXFsYLDtiWHz=1pNdLs7j43fjcx4MkFt9fdrgAijH+vXw@mail.gmail.com> <email@example.com>
> 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.
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.).
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple