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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=u80Rfd9exYvFTlIF8YZJVCKiz5yPc/CBxKkjenSeDIy
	TdYPx66VKBw4ECXV+tQMKhsxENlIOm+PIR0FCSNAKAUj5+KlGdPsHCEfABilJrNY
	QezSY0brBWOC2+9qnLoTeuf8tVYJW+4bPD0pSw2s+wum+6ExLv+Rze2KvcD/PbSc
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=b5RU3A80BjsCGvXBr1wvGIy1eIw=; b=pSy+1TR2oRDbDIXxO
	UbsKw5VOtFafVfMf+PyzSQ1kkw3nK/p/0XBGJap6qYWuj69B/HWLcNSccAZfBnAr
	1UrdEgH+L4k2/vKU8/xYiRwFr10z4g5MyKR+wGEvSw9W5Kd0aPlciOHmBY6E1AFk
	vzIQU2YAohmJstxARjpruW+Igo=
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.6 required=5.0 tests=AWL,BAYES_00,TBC autolearn=no version=3.3.2
X-HELO:	knockando.watchfront.net.uk
Message-ID:	<53050C58.6000008@hones.org.uk>
Date:	Wed, 19 Feb 2014 19:56:08 +0000
From:	Cliff Hones <cliff AT hones DOT org DOT uk>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; 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> <5304FB23 DOT 3000005 AT cygwin DOT com> <1369691347 DOT 20140219231051 AT yandex DOT ru> <530506C9 DOT 6040408 AT cygwin DOT com>
In-Reply-To:	<530506C9.6040408@cygwin.com>
X-Spam-Score:	-0.6 (/) (knockando.watchfront.net.uk)
X-Spam-Report:	knockando.watchfront.net.uk has scanned this email for spam. Results:- RP_MATCHES_RCVD=-0.552 (total -0.6, current threshold 5.0)
X-IsSubscribed:	yes

On 19/02/2014 19:32, Larry Hall (Cygwin) wrote:
> On 2/19/2014 2:10 PM, Andrey Repin wrote:
>> Greetings, Larry Hall (Cygwin)!
>>
>>>   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
>>
>> Larry, we walked through exactly this process, but he denied any investigation
>> by cutting the output of the first echo command.
> 
> You're right Andrey.  You were covering much the same ground with Robert.
> It's strange that he cut off the part of the results that was the key.
> My original inclination was to not step into this thread in the first
> round.  I don't know why I changed my mind for the second. ;-)
> 
> I think the point of Robert's original inquiry was to find out where/how
> the "." could get added if it was happening in Cygwin.  Given the ground
> covered (at least once) in this thread, I think we've provided all the
> information that should be needed to track this down.  If not, the
> remainder of the "where?" and "how?" questions really aren't Cygwin-
> specific so I think this thread is really off-topic.

Perhaps I shouldn't wade in here, but I think the discussion so far has not
focussed on exactly what the OP said.  I also don't understand why he chose
to cut his interesting output to 80 chars, but if you can believe what he says,
which I'll repeat here, there is something odd happening:

He appears to have generated a log file almost as asked - first echoing %PATH% in
a cmd shell, and then appending an invokation of bash with args --login -x -i
His result (cut) was:
> $ head -10 log | cut -c 1-80
> PATH=C:\PROGRAM FILES (X86)\NVIDIA CORPORATION\PHYSX\COMMON;C:\PROGRAM FILES (X8
> bash: cannot set terminal process group (-1): Inappropriate ioctl for device
> bash: no job control in this shell
> + PATH='/usr/local/bin:/usr/bin:/cygdrive/c/PROGRAM FILES (X86)/NVIDIA CORPORATI
> + MANPATH=/usr/local/man:/usr/share/man:/usr/man:
> + INFOPATH=/usr/local/info:/usr/share/info:/usr/info:
> ++ id -un
> + USER=rklemme
> + ORIGINAL_TMP=/cygdrive/c/Users/rklemme/AppData/Local/Temp
> + ORIGINAL_TEMP=/cygdrive/c/Users/rklemme/AppData/Local/Temp

OK - so useless for us - but he goes on to say...

> The first line does not contain the dot.  The fourth line contains the
> dot at the end:
> 
> $ sed -nre '4s#^(.{20}).*(.{80})$#\1...\2#p' log
> + PATH='/usr/local/b...Intel/WirelessCommon:/cygdrive/c/Users/rklemme/Applications/SysinternalsSuite:.'

So there is no dot at the end of PATH as seen in cmd - and (I assume, since this was also discussed)
no duplicated semicolons or trailing semicolon at the end of the cmd PATH.  But the very first
PATH printed by bash does contain a trailing dot.  I assume this is before bash has sourced any
startup scripts - so where does it come from?  Could a trailing unprintable (eg CR) in the path
somehow cause Cygwin dll or bash to add the dot?

I'd suggest if Robert does want to pursue this he (a) reads http://cygwin.com/problems.html, and
submits his cygcheck output (I may have missed it but I don't recall seeing it), and (b) repeats
his diagnostic attempts without cutting, and showing us the full results (not cut or elided).

-- Cliff



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