Thanks, I used the switch /LOG to check what happened when I ran the
dos command from Scilab.
But there is a workaround without an extra file.
My first test command was (the switches are needed when I use it with
a network server):
-->RCcmd
RCcmd =
ROBOCOPY C:\Users\stefan\Documents\test
C:\Users\stefan\Documents\new *.txt /TEE /COPY:DT /XJ /XO /FFT /DST /NP
If I add this to the first command, it works, because the output is
via ECHO:
-->RC2cmd = "FOR /F ""usebackq delims=="" %i IN (`" + RCcmd + "`) DO
@echo %i"
RC2cmd =
FOR /F "usebackq delims==" %i IN (`ROBOCOPY
C:\Users\stefan\Documents\test C:\Users\stefan\Documents\new *.txt
/TEE /COPY:DT /XJ /XO /FFT /DST /NP`) DO @echo %i
But that should be handled by Scilab's functions, at least dos() and
powershell(), shouldn't it?
Regards
Stefan
On 2015-10-28 23:53, JLan wrote:
Workaround:
[reg stat]=unix_g('robocopy C:\A D:\A /LOG:C:\A\log.txt')
[regl statl]=unix_g('type c:\A\log.txt')
J
--
View this message in context:
http://mailinglists.scilab.org/Scilab-users-Windows-shell-command-tp4033045p4033050.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at
Nabble.com.
_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users
