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=AZ6AGQiV12ELnB+A
	rrlq4KbwT3gI6UOmzkTuodnN6KLujHqz24tox0i415rwSVA44ZDfYDOhQbJG2mRO
	gC3ahgzmqFX+R/vu9J4E8sY8N5paJ7ysfFFEw2pq2f83SSh6SN5M37Y379nQ3oCz
	NK5uZNjqtYOkmfAP+oSbxKcFaC8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-id: <5304FB23.3000005@cygwin.com>
Date: Wed, 19 Feb 2014 13:42:43 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT 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 AT cygwin DOT com
Subject: Re: $PATH contains dot but unclear where it comes from
References: <CAM9pMnM1=UnbcXRGefXiDVjVXJcVeNej=OGowbwwWBgHeG+MjQ AT mail DOT gmail DOT com> <CAEhDDbCG7i9GdEE1W2UL9egRdcA786u0xmwsKJXBD5HgXh5XcA AT mail DOT gmail DOT com> <CAM9pMnM-_hZkk5+=44aTKrscqYP-qg1Mv=R4w7Jt2gFjd_WP8w AT mail DOT gmail DOT com> <1811171498 DOT 20140206155616 AT mtu-net DOT ru> <CAM9pMnMBpULHt7NTx-eOr8DmLkQFTQwtTmMpDmbA8UQqLpUh7g AT mail DOT gmail DOT com> <CAM9pMnONy0ua43WKt6yFXzaWyjB4XJmmt7XefYOXer3UYgnEEg AT mail DOT gmail DOT com> <CACUHbYP65+7GJpka9OBAkWnJeRonwNDxbXrG7n06n8e76UhR8g AT mail DOT gmail DOT com> <CAM9pMnM5_LLvA3YaHgzo12wwUzUak2FHzrXug9G=EfD+bdZQgg AT mail DOT gmail DOT com> <5304D694 DOT 9090104 AT cs DOT umass DOT edu> <CAM9pMnMYHrZzV+TFsy7+hqARo0fJgo1o01FKwj_D9UdjD7WajA AT mail DOT gmail DOT com> <5304E874 DOT 20906 AT cygwin DOT com> <CAM9pMnOfTto2QodJeWiEGdLCEPOKHd=_83GFvUzim6d=Rt0V2w AT mail DOT gmail DOT com>
In-reply-to: <CAM9pMnOfTto2QodJeWiEGdLCEPOKHd=_83GFvUzim6d=Rt0V2w@mail.gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 2/19/2014 12:51 PM, Robert Klemme wrote:
> On Wed, Feb 19, 2014 at 6:23 PM, Larry Hall (Cygwin)
>   wrote:
>> On 2/19/2014 12:16 PM, Robert Klemme wrote:
>
>>> 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.
>
> I did look in windows environment as well (again, see earlier emails).

Well, let's consider that you resurrected this thread 12 days after it
fell dormant with no context in that email message for anyone to go on.
If you don't want to have to repeat yourself on individual points as they
are brought up again, you could consider, in the future, summarizing the
current state and things tried when you bring a topic out of hibernation.

>>   Don't discount any start-up batch files
>> (i.e. cygwin.bat), etc., that you may be using to kick-start bash
>> either.
>
> I am using the regular mintty start that cygwin establishes.  This is
> the command line
> C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -
>
> I can't see in documentation that mintty manipulates the environment
> in some way.
>
> More ideas?

 From the Windows "Run..." or "Search programs and files" edit box,
type "cmd.exe".  From the console window that opens as a result, type
the following.

echo %PATH%
c:\cygwin64\bin\bash --norc --noprofile -lix
echo $PATH

Any "." resulting from the second echo?  Anything in the first that
would lead to one?  If it's very obvious that the Windows path isn't
the problem, then exit bash and run it again omitting either --norc
or --noprofile until you zero in on the file in your environment
that's adding the unwanted ".".  Keep in mind that scripts you
have in '/etc/profile.d' are sourced too.  If you've added things
there, this could be the culprit.

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