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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=rCSG93EybvaB1lUTz6WYvip/M1bMoZQpqFO0OOU8v0Z0TqVZ5O/Cn 0dpV0587QFT+vyyh6CSH264WuBMpkmPRWlT9iV1qln6cGRHbSiGqCuTVNrMHUf/v 8YdpWk8aaYXCN0L3FehNTqcwOLWRYxrAIQJqR+QhFjGjgAADn9HZcY= 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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=gu48VqJmOHTwHH/Kaad9Wy8SQ/g=; b=wKostPk50BbSS94Cek0i8x59k/qi nkLP7KfYdQy6fvj70emAtdQ/zRup05vYq8vAmcf9paDPZiaD4e0AzehMsbanhdY2 TZHxNHkG70znspkoFLOqUeochPKT+A7qOJoUW4YeMfN1C5FNcwyWWnM0TTo3KqV2 20BV1ZLQIitEWcg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.1 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: $PATH contains dot but unclear where it comes from Date: Wed, 19 Feb 2014 21:27:25 +0100 Lines: 30 Message-ID: <87ob22n902.fsf@Rainer.invalid> References: <1811171498 DOT 20140206155616 AT mtu-net DOT ru> <5304D694 DOT 9090104 AT cs DOT umass DOT edu> <5304E874 DOT 20906 AT cygwin 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-IsSubscribed: yes Cliff Hones writes: > 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? This is actually from the first non-empty, non-comment line in /etc/profile, where the (converted) windows path is prepended with "/usr/local/bin:/usr/bin:". This suggests that the PATH as seen by bash starts life with that dot appended, but of course it would be more conclusive if the OP had shown the complete output (and maybe truncated the windows PATH variable for the experiment). Looking at the visible PATH it is quite likely that this variable is rather long and the rest of the environment may be quite large also. There are interesting problems when one or both of these get over a certain size – like for example Git, which is using environment variables quite extensively, stopping to work correctly without giving any useful error messages. It probably isn't the problem in this case, but the spaces and parens in the windows path also can become a problem when scripts aren't super careful with their quoting. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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