From: Vince Rice <vrice@solidrocksystems.com>
To: cygwin@cygwin.com
Subject: Re: Requested report
Date: Fri, 01 Dec 2017 15:35:00 -0000 [thread overview]
Message-ID: <18DA4DAE-F801-45B9-9E3D-F03BF7420D07@solidrocksystems.com> (raw)
In-Reply-To: <f4868991-0b26-f80f-805f-eb875b1aa602@gmail.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
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-12-01 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD1QJjXeJxQMS2-mZbF1F8YcKEOa=oa3OtNcEsvTwgEJf9duiw@mail.gmail.com>
2017-11-30 19:12 ` Fwd: " Richard Mateosian
2017-11-30 19:50 ` Andrey Repin
2017-12-01 4:42 ` Richard Mateosian
2017-12-01 14:55 ` cyg Simple
2017-12-01 15:35 ` Vince Rice [this message]
2017-12-01 17:00 ` Brian Inglis
2017-12-02 3:31 ` cyg Simple
2017-12-02 5:07 ` Vince Rice
2017-12-01 22:05 ` Fwd: " Andrey Repin
2017-12-01 18:27 ` Douglas Coup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18DA4DAE-F801-45B9-9E3D-F03BF7420D07@solidrocksystems.com \
--to=vrice@solidrocksystems.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).