system command

[Kenneth Brody]

On 6/18/2016 11:20 AM, Richard Kreiss wrote:
> Why concentrate on the copy command when xcopy offers more granular control.
> As I previously sent, there is an option to display the copy from and to
> names.  That would take care of knowing which file was being copied and
> where it is being copied to.

I'm not so much concerned about the "copy" command versus "xcopy".  I'm more 
concerned about how it appears that even the "echo" command isn't being 
executed.  Nor does it appear that the second "pause" is being executed, 
either.  If something is preventing the command from running, it probably 
doesn't matter if it's "copy" or "xcopy".

[...]
>> On 6/17/2016 4:18 PM, Roland Fischer wrote:
>>> Hi Ken
>>> Nothing displays except the 'Press any key to continue ...'
>>
>> So, even if you add "echo", it doesn't echo anything?
>>
>> It does show a second "press any key to continue" after you press the key,
>> correct?  Or does the second one never show?
>>
>> What happens if you type this at the command prompt?
>>
>>      pause & echo this is the echo command & pause
>>
>> [...]
>>> Try adding an "echo" before the "copy" so you can see what, exactly, was
>> passed:
>>>
>>>   system "pause & echo copy /y c:" { bs { "test.txt testnew.txt & pause"
>>>
>>> Obviously, the command line is being executed, since you get the two
>>> "press any key to continue" messages.
>>
>> What if you remove the first "pause"?
>>
>>      system "echo copy /y c:" { bs { "test.txt testnew.txt & pause"

-- 
Kenneth Brody