This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: bash adds dot to $PATH
- From: Linda Walsh <cygwin at tlinx dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 24 Mar 2014 19:14:52 -0700
- Subject: Re: bash adds dot to $PATH
- Authentication-results: sourceware.org; auth=none
- References: <CAM9pMnPHk+78886DU86tKY6HmOQQUsZLFQk2XoOCMR-aVcUvwg at mail dot gmail dot com> <53186D47 dot 1030709 at cs dot umass dot edu> <CAM9pMnOc9XRk2OqJpuXY7Q7_ZXv+w6RL1LfCO3pAnSOmpXuszA at mail dot gmail dot com> <CAM9pMnNec_Sr2wx+wpvbFTNs3TaJFBioU_tQEzzafyw+rBuSYA at mail dot gmail dot com>
Robert Klemme wrote:
So it could be an OS "feature" but I could not find any
documentation about this. And it is still totally unclear to me what
the criterion might be as bash suffers from this but all other shells
do not. This is weird.
----
I don't think BASH sets the path... it adds to the existing one.
The others may set PATH.
The "." in the path might be the way legacy programs can find their
personal 'libs' in their bin dir, since when most bin's are executed,
the CWD is set to the bindir.
--
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