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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
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: <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>
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)

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