Ha! And I was going to ask if there was one of those fancy names for such a sentence, but you already answered it! :happy:

Agreed, it does sound that way. It's a good one.

That looks real nice; perhaps I'll need to give it a try. :smile: But 'The quick brown fox jumped over a lazy dog.' doesn't contain an 's'. In telecoms, we used to use 'The quick brown fox jumped over the lazy dog's back.' Or, you could use 'The quick brown fox jumps over a lazy dog.' :rolleyes:

That's an extensive batch file! Okay, so at the risk of dating myself, I was building/using computers long before the IBM PC and MS-DOS appeared, so have used many different command consoles, including Linux, and DESQview on MS-DOS. But since finding 4DOS (circa 1992)/4NT/TCC, I've used...

Exactly. And your batch file solves it nicely. Thanks for posting. Strange that my default colours were different than yours. However, I found in the documentation that one can change the colours with an environment variable, which I've now done, since I find the default dark blue and dark...

So, I found this intriguing, and decided to give it a try. Turns out, it didn't work correctly because my GNU utilities were too old (2009). After updating them to the latest, it does work, but for some reason, my grep highlight colour is different than yours; any idea why? But also, with the...

Oh...., got it, thank you.

Thanks both. I decided to go with Scott's suggestion, yielding more flexibility in displayed output: copy /o C:\path1\* \\%NAS\path2\*.jpg > clip: do asset in @clip: iff %@index[%asset,=>] GT 0 then copy /q %@word["=>",0,%asset] \\%NAS\path3\*.jpg echo %@word["=> ",1,%asset] elseiff...

Thanks Vince. Yes, I finally got that far in my reply to Scott (above), as a one-liner, but without the 'set' command. Would the one-liner (above) be improved by including the 'set' command, so that '%@filename[]' would only need to be used once, rather than multiple times as I had it?

But what happens if you have several files in v:\ and in dir1, but dir2 is empty? And you then add a new file to v:. Then the new file in v: gets copied to dir1 (correct), but (for me) all of the files from v: get copied to dir2, whereas what I want is for only the new file to get copied to dir2.

Thanks Scott. Using the echo command, it seems that %f contains the entire path/filename, so therefore that path/filename of course does not exits in the destination path. do f in path1\* (echo %f) shows %f contains the entire path/filename for each file in path1; therefore (if not exist...

This seems to be close but, substituting the copy command for somecommand above, TCC is inserting the entire source path after the destination path. What does 'f' (and '%f') contain: is it the individual filename within the source path, or is it the entire source path/filename?

Hmm... for me, this resulted in all files from v:\ (my path1) being copied to v:\dir2 (my path3). The desired result is for dir1 (my path2) to contain everything that is in v:\ (my path1), but for dir2 (my path3) to contain only new files that were added to dir1 (my path2).

Hi. Using TC/TCC 19.10.54 x64 on Windows 10. In my Windows startup .btm file, I have this line: copy /o C:\path1\* \\%NAS\path2\*.jpg to copy any new files in path1 (they are .jpg files, but have no extension) to path2 on the NAS, giving them a .jpg extension. So, path2 contains a copy of...

Thanks! Solution is to upgrade.:smile: