Gerhard Fiedler wrote:
> Of course. But I repeatedly explained that all the recent doubts here
> about cmd.exe could be resolved by using the exact terms of the doubt;
> no further knowledge was necessary. In all the examples I cited, the
> result was one of the top links in Google using very naive terms, like
> "cmd.exe delayed environment variable extension" or "cmd.exe output to
> environment variable".

Yes, but again, you need to know to ask.  You read the docs you find, see no
mention, and figure it can't be done.  For example, the help page for CMD
discusses delayed variable resolution.  It talks about how it can be enabled
with a command line argument.  There is no hint of any other way to enable
it.  The documenation appears complete, so you figure it can't be done,
until one day you accidentally stumble accross the description in the
SETLOCAL command.

There are many things CMD can't do that appear about as likely as the few
surprising things it can.  You can't possibly be expected to google all
those too, even those that with some stretch of the imagination some command
shells might do on a good day with a full moon in proximity with a dead
fish.

Anyway, I'm not sure what your point it.  I think you're saying we're all
stupid for not having noticed, found, or decided to chase down certain
features in CMD.  Perhaps you're right, but I think the CMD documentation is
largely at fault.  But even if you are right, so what?  OK, we're all
stupid.  Is that what you want to hear?


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist