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