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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=iY
	u+MOcqQ2b2thzAIo9gdbhIdt8IH9kZwr1f9T6RLg/D9plK+Obknnirdp7+2jVZpk
	edHvsoPjvn2nHWZsQFt7sMijByi9/TNQwOG0yesb06ZkmlEZw47ofrYJf1Y+kkos
	70UTnRsKMPEtwEhEM67LWoQH7t4jpnrG6neVMiI3U=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=q4qTVHZH
	lRm+RFOofzzb0Ys3Pfs=; b=IaA9N7jhcVn3gS66oplFsJYiMLf0CIjhOZI+hqiZ
	RLrYNfekWmbXSkwfDfgvvo1IBqgnjTphEu58kKUlOlxKc9SHUrhptz+Z6So6NrWR
	hwGDyElEZFmGgEay1iqODNCoqubi3IUH5kKAmNbiwqgvnLas9TxTblL87WjNwxnf
	+lc=
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=-0.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-lb0-f180.google.com
MIME-Version:	1.0
X-Received:	by 10.152.161.234 with SMTP id xv10mr1287718lab.41.1392799078480; Wed, 19 Feb 2014 00:37:58 -0800 (PST)
In-Reply-To:	<CACUHbYP65+7GJpka9OBAkWnJeRonwNDxbXrG7n06n8e76UhR8g@mail.gmail.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>
Date:	Wed, 19 Feb 2014 09:37:58 +0100
Message-ID:	<CAM9pMnM5_LLvA3YaHgzo12wwUzUak2FHzrXug9G=EfD+bdZQgg@mail.gmail.com>
Subject:	Re: $PATH contains dot but unclear where it comes from
From:	Robert Klemme <shortcutter AT googlemail DOT com>
To:	David Boyce <dsb AT boyski DOT com>, cygwin <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes

On Tue, Feb 18, 2014 at 7:32 PM, David Boyce <dsb AT boyski DOT com> wrote:
>> On Thu, Feb 6, 2014 at 4:32 PM, Robert Klemme
>> <shortcutter AT googlemail DOT com> wrote:
>>
>>> Can anybody make sense of that?  I can share the complete log with
>>> individuals if it helps.
>>
>> Nobody?
>
> I haven't read the whole backthread, but you do understand that a
> missing entry is translated to ".", right? E.g.
> "/usr/bin:$foo:/usr/local/bin" will include a dot if foo is undefined.
> Here's the relevant section from the man page:
>
> "A zero-length (null) directory name in the value of PATH indicates
> the current directory. A null directory name may appear as two
> adjacent colons, or as an initial or trailing colon."

I was not aware of this.  Thank you!

> I'd be surprised if this isn't at the root of the issue.

Let's see: on Windows command prompt

path >path.txt

Now let's look at the contents.  No additional leading or trailing
semi colon.  But:

$ egrep -o ';{2,}' path.txt
;;
;;

Aha!  If we look at the positions

$ egrep -o '.{15};{2,}.{15}' path.txt
OWERSHELL\V1.0\;;C:\PROGRAM FILE
ftware\syswow64;;C:\Program File

we find they do not match the position and mount of dots in the Cygwin
$PATH: it's only present at the end:

mon:/cygdrive/c/Users/rklemme/Applications/SysinternalsSuite:.

OK, now: I removed empty path entries from Windows PATH (system and
user), rebooted and they are gone.

But, the Cygwin shell's $PATH still has the dot at the same position
(i.e. at the end).

I assume there must be some internal mechanism in Cygwin which causes
this but at the moment I am out of ideas where to look further.  Does
anybody else have an idea?  Is there maybe some automatism which adds
the dot because on Windows systems the shell always also looks in the
current directory?

Kind regards

robert


-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

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