View Single Post
  #6  
Old March 20th 20, 04:09 PM posted to microsoft.public.windowsxp.general
JJ[_11_]
external usenet poster
 
Posts: 744
Default "echo one foo=bar" gives an unexpected result. Why ?

On Thu, 19 Mar 2020 09:16:42 +0100, R.Wieser wrote:

I've just done a (bit less than) quick search for a description of what that
"=" sign actually does/is for on the commandline, but got nowhere fast (a
lot of "how to escape it" or "what does it do in a batchfile" stuff though).

The problem (of sorts) is that I can see what it does, but have no idea (and
can't seem to find) what its purpose is. Currently all I have is a "look
people, this is funny!" application of it.

As my google-fu seems to be weak on this, do you have, by any chance, a link
to a description to what its ment for ?


No idea either. There doesn't seem to be any official documentation about it
or the other semicolon and comma delimiters. Not even example of their
specific usage. The leaked Windows NT source codes may shed some light on
this issue.

CMD is a mysterious (or perhaps, buggy) command interpreter. For example, I
found that the "" character when not used for redirection, is treated as
(no quotes) "?.". And the "" character when not used for redirection, is
treated as (no quotes) "*.". At least for DIR command. e.g.

dir ^
dir ^^
dir ^
dir a^

Would be same as:

dir ?.
dir ??.
dir *.
dir a*.
Ads