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=TR
	Ar6ogW5iuQlbOIe3sVdz+uP0D0nsi8MBzqnF9dhKi6Qq/bc8UbmQBdyLl+SqAQXM
	HErDObXohltwVnTklVRQTIg/msWIoI4oPEXfKVukT8iqER95ZQ/thqZm7bnIDIFo
	EOXO0fu1+EYiDQGrsPL5RIJDeqe5DtyKPOQQ8V8qM=
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=q4OJf5+a
	0g9MQ9nwhp2Y0dk+nLw=; b=bouBvHEpN5MZKRBmh3lFE1H3KFYPIIgh8w5UjF/H
	i6Z8srPX9ewCdL5GOUH/6ydbapSYDpnXZ69ByHMzcm+XR5d1KiTFCjEomFb1GScT
	y3onGIXg/Lyx5LBFDtHvIkJUJIsfrsisThQ5Ch+VxybO2ozV2Lpi+Ol4IkUHCRY4
	35w=
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=1.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-la0-f50.google.com
MIME-Version: 1.0
X-Received: by 10.152.209.70 with SMTP id mk6mr51131775lac.13.1395764947178; Tue, 25 Mar 2014 09:29:07 -0700 (PDT)
In-Reply-To: <5330E69C.5010400@tlinx.org>
References: <CAM9pMnPHk+78886DU86tKY6HmOQQUsZLFQk2XoOCMR-aVcUvwg AT mail DOT gmail DOT com>	<53186D47 DOT 1030709 AT cs DOT umass DOT edu>	<CAM9pMnOc9XRk2OqJpuXY7Q7_ZXv+w6RL1LfCO3pAnSOmpXuszA AT mail DOT gmail DOT com>	<CAM9pMnNec_Sr2wx+wpvbFTNs3TaJFBioU_tQEzzafyw+rBuSYA AT mail DOT gmail DOT com>	<5330E69C DOT 5010400 AT tlinx DOT org>
Date: Tue, 25 Mar 2014 17:29:07 +0100
Message-ID: <CAM9pMnOw2fcUFA+CTFpp5YaaYi99KoRS7NAhr+RKhFxhpzBhCA@mail.gmail.com>
Subject: Re: bash adds dot to $PATH
From: Robert Klemme <shortcutter AT googlemail DOT com>
To: cygwin <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes

On Tue, Mar 25, 2014 at 3:14 AM, Linda Walsh wrote:
> Robert Klemme wrote:
>   So it could be an OS "feature" but I could not find any
>>
>> documentation about this. And it is still totally unclear to me what
>> the criterion might be as bash suffers from this but all other shells
>> do not. This is weird.
>
> ----
> I don't think BASH sets the path... it adds to the existing one.

Please read the other emails - all the information is there.

> The others may set PATH.
>
> The "." in the path might be the way legacy programs can find their
> personal 'libs' in their bin dir, since when most bin's are executed,
> the CWD is set to the bindir.

Yes, probably. But why do some processes have it added and some not? I
even tried searching for information on such a feature on Microsoft
sites but did not find anything. I can imagine Windows doing this kind
of magic, but I haven't found any documentation about this -
especially what properties a process needs to have for this automatism
to kick in.

Cheers

robert


-- 
[guy, jim].each {|him| remember.him 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