If /i "%~1"="-help" call :header & call :usage "%~2" & goto :end If "%~1"="full" call :header & goto :eofĮcho **** MISSING "REQUIRED ARGUMENT" **** f, -flag value specifies a named parameter value >template.bat -verbose "argument #1" -flag "my flag" secondĮcho This is a sample batch file template,Įcho providing command-line arguments and flags.Įcho %_BAT_NAME% "required argument" "optional argument"Įcho. Test.bat "required argument" "optional argument" Providing command-line arguments and flags. The jist of it is having the :init, :parse, and :main functions. As well as supporting the following structures: >template.bat arg1 This technique has a bit of overhead as you'll see, but it makes my batch files very easy to understand and quick to implement. The FOR /F should work with delayed expansion off, else contents with "!" would be destroyed.Īfter removing the extra characters in param1, you got it.Īnd to use param1 in a safe way, enable the delayed expansion.Ī friend was asking me about this subject recently, so I thought I'd post how I handle command-line arguments in batch files. Then reading the rem parameter output from the file, but carefully. Or a caret ^ at the line end could work as a multiline character, even in after a rem. The extra characters * # are used to be safe against contents like /? (would show the help for REM).
So even "&"& could be echoed without producing an error, as it is remarked.īut to be able to redirect the output of the echo on, you need the two for-loops.
The trick is to enable echo on and expand the %1 after a rem statement (works also with %2. It can be solved with reading from a temporary file a remarked version of the parameter. set var=%1Īnd each line fails, as one of the & is outside of the quotes. There is no simple way for complex contents like "&"^&, as it's not possible to access %1 without producing an error. Accessing batch parameters can be simple with %1, %2.
0 kommentar(er)
