Suggestion for a future version: Allow the vertical bar | as an include-list separator, behaving just the same as the semicolon. Then in some more-distant-future version, the semicolon could be deprecated.... Filespecs containing a vbar would need to be quoted, of course, just like spaces, ampersands, et cetera.
(The choice of semicolon for this function goes back to 4DOS. IIRC, semicolon was not a legal filename character in DOS, so it made sense at the time.)
You already have that part implemented. A vertical bar between quotes has no special meaning.
Code:
C:\>dir "*.bat|*.cmd|*.btm"
Volume in drive C is Hard Drive Serial number is 6218:b594
TCC: (Sys) The system cannot find the file specified.
"C:\*.bat|*.cmd|*.btm"
0 bytes in 0 files and 0 dirs
156,308,537,344 bytes free
C:\>
I didn't quite have that figured out. Using TOUCH /C "a;b;c", if any exist it'll touch (only) them; in none exist, it'll create only the last one specified.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.