Re: Requested report

[Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>]

On 2017-12-01 08:35, 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.
Some of these packages include Cygwin RT under the covers as an install base,
and to support Ruby Gems, which is why we keep seeing FAST_CWD complaints.

>> 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.).
+1 post TC AST/Uwin, BCpp GNUtilities, DJgpp, GnuWin32, MinGW, Msys, ...
...elevated System Scheduled Tasks using shell scripts...

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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