X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=YY1PdPY1+Pg/giOd
	kH0nrkeKVIup7GH/H4SuVR12MlT9py4uiF6mThDwA35d3buMC9LKG0T8a7gFCtkt
	hYqHIKS7+KgtCBfMJqo+jLb2sL7xIzfGgRtMcxNObGVKHTqm/Do7DMdrwToojxal
	m8p+21OV46HpSGOTBkonbrFy+hQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=G7yUi40s0rWusRDmbWARue
	LY1HI=; b=Ij172NZ7eQyXjU+u84DjIq7kaTnIQvkl9Yhaiz9xEBI6Hc5pwGTryx
	TLuD2yKX4jseuvgvSwIzsXZIQsFW4TbRlvrYaO+2LQ23RokvRef2lMntQCIxVZ6I
	+8AVpdWIwQ3TaWvu5RzxfNyZFlaAV3Mlb390CLlac6UbsILtD5ES4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.6 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_BL_SPAMCOP_NET,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtpback.ht-systems.ru
Date:	Thu, 20 Feb 2014 02:23:04 +0400
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<937868018.20140220022304@yandex.ru>
To:	"Larry Hall (Cygwin)" <cygwin AT cygwin DOT com>
Subject:	Re: $PATH contains dot but unclear where it comes from
In-Reply-To:	<53051EE4.20803@cygwin.com>
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> <5304FB23 DOT 3000005 AT cygwin DOT com> <1369691347 DOT 20140219231051 AT yandex DOT ru> <530506C9 DOT 6040408 AT cygwin DOT com> <53050C58 DOT 6000008 AT hones DOT org DOT uk> <87ob22n902 DOT fsf AT Rainer DOT invalid> <53051EE4 DOT 20803 AT cygwin DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Larry Hall (Cygwin)!

> It's certainly possible that there is a pathological case where the Windows
> path isn't handled properly because of size, content, or other unforeseen
> case.

I can offer one idea of where this problem could originate from, which is in
no way pathological (i mean, in code, but comes from brain pathology of the
person introduced this problem into settings).
Windows PATH variable is constructed from two parts upon loading of user
profile.
First part is a system PATH in /proc/registry/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session\ Manager/Environment/PATH
The other part is a user's PATH in /proc/registry/HKEY_CURRENT_USER/Environment/PATH
Both parts are, by no surprise, concatenated by semicolon.
Now, if some brain-dead programmer set an installation routine to append
"some\path;" to the end of either variable, you will get an empty element in
the path. Either "..;;..." or "...;".

> But if there is a problem like this in Cygwin, we certainly need the
> specifics to show us all the problem.  That's not to say that if this issue
> tickles someone enough, they shouldn't investigate it more in an attempt
> to get to the bottom of it.  But absent that, I think it makes sense to let
> Robert show us that this is definitely some Cygwin-specific problem which
> could bite anyone with the same conditions.  At that point, it's definitely
> something worth talking about more.
So far, I'm not convinced that issue is Cygwin-specific. The fact that it
doesn't manifest in Windows is actually because of it's (windows) native
ignorance for this matter.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 20.02.2014, <02:14>

Sorry for my terrible english...


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

- Raw text -