Greetings, Robert Klemme! > On Wed, Feb 19, 2014 at 6:23 PM, Larry Hall (Cygwin) > wrote: >> On 2/19/2014 12:16 PM, Robert Klemme wrote:
>>> The dot is already in the variable before bash even modifies it. >> >> So that means you need to look in your Windows environment to understand >> where this comes from. > I did look in windows environment as well (again, see earlier emails). >> Don't discount any start-up batch files >> (i.e. cygwin.bat), etc., that you may be using to kick-start bash >> either. > I am using the regular mintty start that cygwin establishes. This is > the command line > C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico - > I can't see in documentation that mintty manipulates the environment > in some way. > More ideas? The problem really was there: $ head -10 log | cut -c 1-80 PATH=C:\PROGRAM FILES (X86)\NVIDIA CORPORATION\PHYSX\COMMON;C:\PROGRAM FILES (X8 You cut the output, denying any further investigation. -- WBR, Andrey Repin (anrdae...@yandex.ru) 19.02.2014, <22:27> Sorry for my terrible english... -- 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