RE: Problems with echo. (echo period)

[Dave Korn]

On 24 April 2007 20:36, Earnie Boyd wrote:

> Quoting Aaron Shatters:
> 
>> 2 - using "echo. 2>&1" which tricks make into thinking this should be
>> handled by the shell?
> 
> I hate to be the bearer of bad news but ``echo.'' isn't a valid command.

[  Just to give a straight answer: It's documented as so on the MSDN page 
linked upthread.  ]
 
> <snippet>
> C:\>dir echo*
> Volume in drive C is QWEST
> Volume Serial Number is 6077-E76C
> 
> Directory of C:\
> 
> File Not Found
> 
> C:\>echo. > echo.
> 'echo.' is not recognized as an internal or external command,
> operable program or batch file.


  Heh, thats cute.  A very cleverly manipulated experimental setup for 
rhetorical purposes!  How long'd it take you to figure out that the redirected 
output file gets opened before the path search is done?


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\dk>cd \

C:\>echo.


C:\>notepad echo.
                 [ typed 'foo!' and saved and exited]
C:\>type echo.
foo!

C:\>echo.
'echo.' is not recognized as an internal or external command,
operable program or batch file.

C:\>del echo.

C:\>echo.


C:\>echo. > echo.
'echo.' is not recognized as an internal or external command,
operable program or batch file.

C:\>del echo.

C:\>echo. > ohce.

C:\>echo.


C:\>type ohce.
Earnie is a troll!



C:\>


  Wow!  That wasn't what I expected!  I wonder how that got there?

  <g>

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....