start.cmd: fixed parameters --input bug

It appears that from the ploygot script, the --input parameter name is conflicting with the PowerShell "input" name and "path", according to Joly0. Hence, this caused an inconsistency from the end-user side where the provided "input" or "path" is not the correct one as reported by Geoff McQueen. This patch fixes the parameters --input naming convention bug as stated above in the start.cmd polygot script. Reported-by: Geoff McQueen [https://github.com/geoff-m] Signed-off-by: Joly0 <[email protected]> Accepted-by: (Holloway) Chew, Kean Ho <[email protected]> Reworded-by: (Holloway) Chew, Kean Ho <[email protected]> Reviewed-by: (Holloway) Chew, Kean Ho <[email protected]> Signed-off-by: (Holloway) Chew, Kean Ho <[email protected]>
hollowaykeanho · Oct 3, 2024 · fb8b8de · fb8b8de
1 parent 305efd3
commit fb8b8de
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/start.cmd b/start.cmd
@@ -55,8 +55,8 @@ IF "%*"=="" ( goto :empty )
 set location=%~dp0init\windows.ps1
 set location="%location%"
 set _parameters=%*
+set _parameters=!_parameters: --input= --path!
 set _parameters=!_parameters:--=-!
-set _parameters=!_parameters:input=path!
 set _parameters=!_parameters:"=\"!
 call Powershell.exe -NoProfile -executionpolicy bypass -Command "& '%location%' %_parameters%"
 EXIT /B