Seems that @execstr[] behaves differently on Win10 than on earlier versions.
I have the following alias:
alias du=`*echo %@word[" ",0-7,%@execstr[-2,*dir/suk %1]]`
This prints something like ".... bytes in ... files and ... dirs" on Win 7 and "ECHO is OFF" on Win10.
Drilling deeper, the negative line number in @execstr[] doesn't work. No matter which negative number I specify in "echo %@execstr[n,dir]", I get "ECHO is OFF".
I am sing 20.00.16. Same results seen with build 15. (Actually, tested b15 and b16 on Win10, and b14 and b16 on Win7). Windows 7 and 10 are Pros.
Ideas? Thanks
I have the following alias:
alias du=`*echo %@word[" ",0-7,%@execstr[-2,*dir/suk %1]]`
This prints something like ".... bytes in ... files and ... dirs" on Win 7 and "ECHO is OFF" on Win10.
Drilling deeper, the negative line number in @execstr[] doesn't work. No matter which negative number I specify in "echo %@execstr[n,dir]", I get "ECHO is OFF".
I am sing 20.00.16. Same results seen with build 15. (Actually, tested b15 and b16 on Win10, and b14 and b16 on Win7). Windows 7 and 10 are Pros.
Ideas? Thanks