make-w32
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with echo. (echo period)


From: Aaron Shatters
Subject: Re: Problems with echo. (echo period)
Date: Thu, 19 Apr 2007 08:23:49 -0700 (PDT)

>> For everyone who has 'echo""' working, I have an explaination...
>> 
>> You probably have the echo.exe available in PATH somewhere.  Let me show
>> you... 
>> 
>> #########################################################
>> Microsoft Windows 2000 [Version 5.00.2195]
>> (C) Copyright 1985-2000 Microsoft Corp.
>> P:\>set PATH=
>> P:\>echo""
>> 'echo""' is not recognized as an internal or external command,
>> operable program or batch file.
>> P:\>set PATH=C:\cygwin\bin
>> P:\>echo""
>> 
>> P:\>
>> #########################################################
>  Hmm, that's interesting; I do have cygwin echo in my PATH, but that doesn't
>explain why I get this:
>#########################################################
>C:\Documents and Settings\dk>set PATH=C:\cygwin\bin
>C:\Documents and Settings\dk>echo""
>
>C:\Documents and Settings\dk>echo --help
>--help
>C:\Documents and Settings\dk>C:\cygwin\bin\echo --help
>Usage: /usr/bin/echo [OPTION]... [STRING]...
>Echo the STRING(s) to standard output.
>  -n             do not output the trailing newline
>  -e             enable interpretation of backslash escapes
>  -E             disable interpretation of backslash escapes (default)
>      --help     display this help and exit
>      --version  output version information and exit
>If -e is in effect, the following sequences are recognized:
>  \0NNN   the character whose ASCII code is NNN (octal)
>  \\     backslash
>  \a     alert (BEL)
>  \b     backspace
>  \c     suppress trailing newline
>  \f     form feed
>  \n     new line
>  \r     carriage return
>  \t     horizontal tab
>  \v     vertical tab
>NOTE: your shell may have its own version of echo, which usually supersedes
>the version described here.  Please refer to your shell's documentation
>for details about the options it supports.
>Report bugs to <address@hidden>.
>C:\Documents and Settings\dk>
>>#########################################################

You are still in the cmd.exe shell.  If the shell recognizes it, it will not 
look on the PATH.  If the shell doesn't recognize it as being a shell command 
(ie. 'echo""') then it will look for an executable in the PATH somewhere.  I 
guess that the logic cmd.exe uses for determining if it is a shell command is 
different than the logic for determining if there is an executable that exists.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]