From: Vincent B. <vin...@ho...> - 2012-10-12 19:45:34
|
>On Thu, Oct 11, 2012 at 3:46 PM, Vincent Belaïche wrote: >> Hello, >> > >[...] > > >> >> However, if I replace `ECHO.' by `echo.', i.e. go to lower case, then >> the problem disappears. > >I don't think this is a bug but a feature. What is a command of >``echo.''? Remove the period (.) character and it works. > > > >BTW, I get the same error with both ECHO. and echo. so you must have a >binary named echo in the PATH if it works for you. > >-- >Earnie >-- https://sites.google.com/site/earnieboyd > [...] Dear Earnie, `echo.' and `echo' are not exactly the same command: `echo. Hello' will output ` Hello', whereas `echo Hello' will output `Hello'. If you want to output some text containing some identation like this: 1. First point is indented like that - it has some sub-item here - and some other here 2. Second point what you will do is: ECHO 1. First point ECHO. is indented like that ECHO. - it has some sub-item here ECHO. - and some other here ECHO 2. Second point and not ECHO 1. First point ECHO is indented like that ECHO - it has some sub-item here ECHO - and some other here ECHO 2. Second point because the latter would not produce the expected result but instead: 1. First point is indented like that - it has some sub-item here - and some other here 2. Second point Concerning the fact that you get the same error with ECHO. and echo., you are correct, I had GnuWin32 in my path, and this contains a command named echo.exe doing the job properly. VBR, Vincent. |