This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: $PATH contains dot but unclear where it comes from
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 19 Feb 2014 21:27:25 +0100
- Subject: Re: $PATH contains dot but unclear where it comes from
- Authentication-results: sourceware.org; auth=none
- 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> <53050C58 dot 6000008 at hones dot org dot uk>
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