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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 20 Feb 2014 02:23:04 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <937868018.20140220022304@yandex.ru>
To: "Larry Hall (Cygwin)" <cygwin@cygwin.com>
Subject: Re: $PATH contains dot but unclear where it comes from
In-Reply-To: <53051EE4.20803@cygwin.com>
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> <5304E874.20906@cygwin.com> <CAM9pMnOfTto2QodJeWiEGdLCEPOKHd=_83GFvUzim6d=Rt0V2w@mail.gmail.com> <5304FB23.3000005@cygwin.com> <1369691347.20140219231051@yandex.ru> <530506C9.6040408@cygwin.com> <53050C58.6000008@hones.org.uk> <87ob22n902.fsf@Rainer.invalid> <53051EE4.20803@cygwin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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@yandex.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