DosTips.com

That is also valuable and instructive, and provides rich context and valuable, instructive examples. Thank you.

I feel short of words in responding. I consulted AI, and the answer is... (As expressed by character Jeff Spicoli of "Fast Times at Ridgemont High") "Awesome! Totally awesome!" That's everything that I could ask for AFAIAC. I incorporated in my .bat calling .bat and success. Solved. I observed somet...

Let me add, about redirection, some of you who are highly comfortable and proficient with redirection and piping might be thinking "he's shooting himself in the foot because piping (DIR A*.) is certainly the expedient answer". If so, okay, I'll do it the "right" way. It's just that if I can simply a...

FOR /R puzzler? (wildcarded folders only, e.g. A*) I have c:\JOE\ALAN, c:\JOE\ALBERT, c:\JOE\ANNA, c:\JOE\BOB Launching from \JOE\, I want to findstr every file hat.txt that contains the string {cat} (no braces), but only for DIRs that begin with the letter A; and include the DIR in the output, perh...

Thank you - similar to my new understanding that %~p is "already" effectively quoted if there are spaces, but not if there is an ampersand even if there are spaces.

I don't know what I would have done without you guys.

Anyway, I see that you used double quoting. It new works when surrounding with double quotes.

The double quoting wasn't necessary when embedded spaces were in the folder name, but were with the ampsersand. Thanks for getting me to that solution.

(deleted)

I apologize in advance if this has been covered. I bled mucho time searching before posting. I am finding that the "p" in the magic substitution string %%~_1 causes processing failure if an ampersand is in the DIR name, e.g. c:\my dog & pony This is on Win 10, regular CMD, .BAT. %1 is foo.txt (or fo...

BTW, the reason I ended up with "7*" anyway was from a batch %1. The user went foo.bat 7* under the understandable notion that it would return anything with a 7 in it. Methinks I'll need to disallow asterisks in %1 for this project.There's too much risk that the user will either use .* when * is nec...

Just a quick note, suddenly underwater here on other projects... Thank you for your [as always] steady, precise and thorough, and insightful performance. What can I say. I solved my issue with character class -- user error, surprise, surprise. And I can explain why I reached the silly-sounding concl...

What a work of art! I'll need to come back to this when I can put in some time but I'll mention a few things - Yes, /OD within each folder is what I'm accustomed to and my initial intent was to see the /OD grouped sorts, though the other everything at once way SOMETIMES is what I prefer (which I've ...

Note I found Dave's https://ss64.com/nt/findstr-linebreaks.html "FINDSTR - Searching across Line Breaks" but it is confusing where he says "I can't graphically represent the characters" and I don't understand why he shows !CR!*!LF! instead of $^ but anyway that didn't work either - it did not report...

I have a .BAT that reports every found "a.txt" and directory names via something like dir /a /od /s *.* | FINDSTR /I /R /C:"a.txt" /C:" Directory of " (As you maybe guessed I'm using this construct to avoid "false positives" on short file names. It's actually more complex than this but this will suf...

I have [at least one] irritating file, C:\Windows\SoftwareDistribution\DataStore\DataStore.edb that produces a runaway FINDSTR. (FWIW, the input file is over 2G.) Stderr begins with FINDSTR: Line 2 is too long. FINDSTR: Line 2 is too long. FINDSTR: Line 2 is too long. FINDSTR: Line 3 is too long. FI...

Think of the basic FAT and file system architecture. If I add a file A.TXT to c:\foo, nothing in the file system need change for FOO entries (at least, never needed to until "last accessed" came into being). A file entry for A.TXT with that creation date is created; but that alone would be no reason...