| 1. |
Solve : Filename Glitch with "FOR" When Directing Output of Decompiler to TXT File? |
|
Answer» This should be a piece of cake for you folks, I'm trying to use "FOR" to decompile a bunch of files using a 3rd party decompiler. What I'm using works, but the filename of the output isn't coming out like I want it to, here's my command: I guess in this case it's %~nf just because I used %f rather than %I as my variable? Yes, Jim. Glad to see it helped.Quote from: JRobinson on June 22, 2013, 02:46:52 AM I guess in this case it's %~nf just because I used %f rather than %I as my variable? In the examples in the FOR documentation, the character I (upper case i) is used as a placeholder for whatever letter you choose to use. Quote from: Salmon Trout on June 23, 2013, 06:22:56 AM In the examples in the FOR documentation, the character I (upper case i) is used as a placeholder for whatever letter you choose to use. It's funny that. I learned in programming never to use an i I l 1 or o 0 O as a variable name because in in some fonts you can't tell which is which. Programmers of today don't seem to have learned that - and it being MICROSOFT makes it even more of an oversight. Quote from: foxidrive on June 23, 2013, 07:02:55 AM I learned in programming never to use an i I l 1 or o 0 O as a variable name because in in some fonts you can't tell which is which. I have noticed that lots of example code uses lower case i or j as loop counters... I just confirmed you can use a pipe symbol in cmd provided you escape it: Code: [Select]for %^| in (*.*) do @echo %^| Code: [Select]@echo off for %%^| in (*.bat) do echo %%^| That's surprising. I hate when people use things like %%# and especially %%? to confuse the newbies with wildcards.Quote from: foxidrive on June 23, 2013, 07:59:50 AM That's surprising.But Jeb writes some pretty wicked batch files.That's for sure. |
|