DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=JVytBIp7YqwtzXJ3
	eKVjsTn1k70Z1Br/alSmKkEOopvqTOEGCToTNXhTF+Io+eG4zXYEVVcJEVNdhBh0
	NrHeTjgQl5e1quT3tbSgpFNFyguTJY1hou1ETO0GpW6D7aLpzOnWHmAjkjEX+Fsr
	TUb0Z7NIqA2K7lT+jXGmb2cQZOQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-id: <5304E874.20906@cygwin.com>
Date: Wed, 19 Feb 2014 12:23:00 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
Reply-to: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: $PATH contains dot but unclear where it comes from
References: <CAM9pMnM1=UnbcXRGefXiDVjVXJcVeNej=OGowbwwWBgHeG+MjQ@mail.gmail.com> <CAEhDDbCG7i9GdEE1W2UL9egRdcA786u0xmwsKJXBD5HgXh5XcA@mail.gmail.com> <CAM9pMnM-_hZkk5+=44aTKrscqYP-qg1Mv=R4w7Jt2gFjd_WP8w@mail.gmail.com> <1811171498.20140206155616@mtu-net.ru> <CAM9pMnMBpULHt7NTx-eOr8DmLkQFTQwtTmMpDmbA8UQqLpUh7g@mail.gmail.com> <CAM9pMnONy0ua43WKt6yFXzaWyjB4XJmmt7XefYOXer3UYgnEEg@mail.gmail.com> <CACUHbYP65+7GJpka9OBAkWnJeRonwNDxbXrG7n06n8e76UhR8g@mail.gmail.com> <CAM9pMnM5_LLvA3YaHgzo12wwUzUak2FHzrXug9G=EfD+bdZQgg@mail.gmail.com> <5304D694.9090104@cs.umass.edu> <CAM9pMnMYHrZzV+TFsy7+hqARo0fJgo1o01FKwj_D9UdjD7WajA@mail.gmail.com>
In-reply-to: <CAM9pMnMYHrZzV+TFsy7+hqARo0fJgo1o01FKwj_D9UdjD7WajA@mail.gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 2/19/2014 12:16 PM, Robert Klemme wrote:
> On Wed, Feb 19, 2014 at 5:06 PM, Eliot Moss <moss@cs.umass.edu> wrote:
>> As others have said, cygwin does not add . to the path
>> itself.  It must be something in your .bash_profile,
>> .bashrc, or other script sourced from them.
>>
>> Going through the output of your login with tracing
>> enabled, as previously described, really is a straightforward
>> way to track this down ...
>
> You are right - that's why I did that already.  You would have found
> out by reading earlier emails. But to no avail.  As I have written
> already the very first line of the log looks like this
>
> + PATH='/usr/local/bin:/usr/bin:/cygdrive/c/PROGRAM FILES (X86)/NVIDIA
> CORPORATION/PHYSX/COMMON:/cygdrive/c/PROGRAM FILES (X86)/INTEL/ICLS
> CLIENT:/cygdrive/c/PROGRAM FILES/INTEL/ICLS CLIENT:/cygdrive/c/PROGRAM
> FILES (X86)/RSA SECURID TOKEN COMMON:/cygdrive/c/PROGRAM FILES/COMMON
> FILES/MICROSOFT SHARED/WINDOWS LIVE:/cygdrive/c/PROGRAM FILES
> (X86)/COMMON FILES/MICROSOFT SHARED/WINDOWS
> LIVE:/cygdrive/c/Windows/SYSTEM32:/cygdrive/c/Windows:/cygdrive/c/Windows/SYSTEM32/WBEM:/cygdrive/c/Windows/SYSTEM32/WINDOWSPOWERSHELL/V1.0:/cygdrive/c/PROGRAM
> FILES/DELL/DELL DATA PROTECTION/ACCESS/ADVANCED/WAVE/GEMALTO/ACCESS
> CLIENT/V5:/cygdrive/c/PROGRAM FILES (X86)/NTRU CRYPTOSYSTEMS/NTRU TCG
> SOFTWARE STACK/BIN:/cygdrive/c/PROGRAM FILES/NTRU CRYPTOSYSTEMS/NTRU
> TCG SOFTWARE STACK/BIN:/cygdrive/c/PROGRAM FILES (X86)/WINDOWS
> LIVE/SHARED:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE
> COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT
> ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R)
> MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES
> (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE
> COMPONENTS/IPT:/cygdrive/c/Program Files/WIDCOMM/Bluetooth
> Software:/cygdrive/c/Program Files/WIDCOMM/Bluetooth
> Software/syswow64:/cygdrive/c/Program Files (x86)/Intel/OpenCL
> SDK/2.0/bin/x86:/cygdrive/c/Program Files (x86)/Intel/OpenCL
> SDK/2.0/bin/x64:/cygdrive/c/Program Files/Intel/Intel(R) Management
> Engine Components/DAL:/cygdrive/c/Program Files/Intel/Intel(R)
> Management Engine Components/IPT:/cygdrive/c/Program Files
> (x86)/Intel/Intel(R) Management Engine
> Components/DAL:/cygdrive/c/Program Files (x86)/Intel/Intel(R)
> Management Engine Components/IPT:/cygdrive/c/Program
> Files/Intel/WiFi/bin:/cygdrive/c/Program Files/Common
> Files/Intel/WirelessCommon:/cygdrive/c/Users/rklemme/Applications/SysinternalsSuite:.'
>
> It's from /etc/profile and the line looks like this
>
> PATH="/usr/local/bin:/usr/bin:${PATH}"
>
> The dot is already in the variable before bash even modifies it.

So that means you need to look in your Windows environment to understand
where this comes from.  Don't discount any start-up batch files
(i.e. cygwin.bat), etc., that you may be using to kick-start bash
either.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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