Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Windows echo: (5 Items)
   
Windows echo  
With IDE 4.5.0 The echo command under Windows doesn't seems to process \c anymore. Instead of not doing a line feed \c 
is being displayed
Re: Windows echo  
Mario Charest wrote:
> With IDE 4.5.0 The echo command under Windows doesn't seems to process \c anymore. Instead of not doing a line feed \c
 is being displayed

echo.exe is still interpreting escape sequences in 6.4

C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\cbar"
foo
C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\cbar"
foo
C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\nbar"
foo
bar

C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\nbar"
foo
bar

Regards,

Ryan Mansfield
Re: Windows echo  
Look like I jumped to conclusion too fast.  Further investigation shows that the issue is with PATH.  Here is what 
happen:

Install 6.3.2
Install 6.4.0
Switch config to 6.3.2
Install ch ( C Shell)

Ch modifies the path variable and add its own directory. Because it was installed after the switch to 6.3.2 the path for
 ch ended up at the end of PATH.

When I switched back to 6.4.0 PATH gets modified but the QNX component of the path is not replace, it's first remove and
 then the 6.4.0 get added at the end.  The results is that the order is changed, resulting in chaos.

After switching to 6.4.0 echo was not the one from the 6.4.0 but rather from ch.  I'm even afraid it could be the one 
coming windows itself.  I guess the solution is to prefix all commands in our makefile with $QNX_HOST



> Mario Charest wrote:
> > With IDE 4.5.0 The echo command under Windows doesn't seems to process \c 
> anymore. Instead of not doing a line feed \c is being displayed
> 
> echo.exe is still interpreting escape sequences in 6.4
> 
> C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\cbar"
> foo
> C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\cbar"
> foo
> C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\nbar"
> foo
> bar
> 
> C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\nbar"
> foo
> bar
> 
> Regards,
> 
> Ryan Mansfield


Re: Windows echo  
Having not followed this thread closely could you not simply set path explicitly at the beginning of your scripts?

Mario Charest wrote:
> Look like I jumped to conclusion too fast.  Further investigation shows that the issue is with PATH.  Here is what 
happen:
> 
> Install 6.3.2
> Install 6.4.0
> Switch config to 6.3.2
> Install ch ( C Shell)
> 
> Ch modifies the path variable and add its own directory. Because it was installed after the switch to 6.3.2 the path 
for ch ended up at the end of PATH.
> 
> When I switched back to 6.4.0 PATH gets modified but the QNX component of the path is not replace, it's first remove 
and then the 6.4.0 get added at the end.  The results is that the order is changed, resulting in chaos.
> 
> After switching to 6.4.0 echo was not the one from the 6.4.0 but rather from ch.  I'm even afraid it could be the one 
coming windows itself.  I guess the solution is to prefix all commands in our makefile with $QNX_HOST
> 
> 
> 
>> Mario Charest wrote:
>>> With IDE 4.5.0 The echo command under Windows doesn't seems to process \c 
>> anymore. Instead of not doing a line feed \c is being displayed
>>
>> echo.exe is still interpreting escape sequences in 6.4
>>
>> C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\cbar"
>> foo
>> C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\cbar"
>> foo
>> C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\nbar"
>> foo
>> bar
>>
>> C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\nbar"
>> foo
>> bar
>>
>> Regards,
>>
>> Ryan Mansfield
> 
> 
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post18814
> 

-- 
cburgess@qnx.com
RE: Windows echo  

> -----Original Message-----
> From: Colin Burgess [mailto:community-noreply@qnx.com]
> Sent: January-20-09 3:40 PM
> To: general-ide
> Subject: Re: Windows echo
> 
> Having not followed this thread closely could you not simply set path
> explicitly at the beginning of your scripts?

Guess I could but I prefer to have each command point exactly where I want them to.

> 
> Mario Charest wrote:
> > Look like I jumped to conclusion too fast.  Further investigation
> shows that the issue is with PATH.  Here is what happen:
> >
> > Install 6.3.2
> > Install 6.4.0
> > Switch config to 6.3.2
> > Install ch ( C Shell)
> >
> > Ch modifies the path variable and add its own directory. Because it
> was installed after the switch to 6.3.2 the path for ch ended up at the
> end of PATH.
> >
> > When I switched back to 6.4.0 PATH gets modified but the QNX
> component of the path is not replace, it's first remove and then the
> 6.4.0 get added at the end.  The results is that the order is changed,
> resulting in chaos.
> >
> > After switching to 6.4.0 echo was not the one from the 6.4.0 but
> rather from ch.  I'm even afraid it could be the one coming windows
> itself.  I guess the solution is to prefix all commands in our makefile
> with $QNX_HOST
> >
> >
> >
> >> Mario Charest wrote:
> >>> With IDE 4.5.0 The echo command under Windows doesn't seems to
> process \c
> >> anymore. Instead of not doing a line feed \c is being displayed
> >>
> >> echo.exe is still interpreting escape sequences in 6.4
> >>
> >> C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\cbar"
> >> foo
> >> C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\cbar"
> >> foo
> >> C:\>C:/QNX630/host/win32/x86/usr/bin/echo.exe "foo\nbar"
> >> foo
> >> bar
> >>
> >> C:\>C:/QNX640/host/win32/x86/usr/bin/echo.exe "foo\nbar"
> >> foo
> >> bar
> >>
> >> Regards,
> >>
> >> Ryan Mansfield
> >
> >
> >
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post18814
> >
> 
> --
> cburgess@qnx.com
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20448
>