Home/ Questions/Q 7693149
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T21:01:03+00:00

This ended up being a path issue. I was using path as one of

  • 0

This ended up being a path issue. I was using “path” as one of my variables elsewhere in the script without realizing that this actually edited the environment variable PATH.

Original question:

I am writing a batch file. In the batch file I have the following:

FOR /F "tokens=*" %%a IN ('git branch -r') DO CALL :SOMELABEL %%a

EXIT

:SOMELABEL
git status
START /B /WAIT CMD /C git status
FOR /F "tokens=*" %%n IN ('git status') DO ECHO %%n
GOTO :EOF

‘git status’ is just an example. Each of the 3 ‘git status’ commands return “‘git’ is not recognized as an internal or external command, operable program or batch file.”

Normally, this would be an environment variable issue (PATH), but what makes this unique is the fact that the first git command works (“git branch -r”). I have maybe 5 other batch files that can use the git command successfully as well. Any ideas as to why the later git commands won’t work in the code above?

If it’s due to a permissions issue (like can’t execute another git command while one is in progress sort of thing), any idea how I might make this script work (preferably without having to make a temporary file)? Or is making a temp file for the output of the first command the only way?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It should be a PATH issue, though.

    The OP Lectrode confirms:

    It was a path issue.
    I just realized that in my original script I was using path for one of my variables.
    I did not realize that was setting the environment PATH variable.

    Apparently git uses that “batch proxy” thing.
    The command works when you change git status to CALL git status.

    Original answer:

    I just tested the following script successfully, following the syntax described in “DOS Batch – Function Tutorial” (and using the ‘which’ command I installed through gow):

    @echo off
echo.PATH=%PATH%
which git.exe
FOR /F "tokens=*" %%a IN ('git branch -r') DO CALL :myDosFunc %%a
call:myDosFunc
echo.&pause&goto:eof

:myDosFunc    - here starts my function identified by it`s label
echo. with param  %~1
which git.exe
git status
goto:eof

    And it did returned, when executed within a Git repo on Windows:

    C:\prog\git\tests\my_repo>..\c.bat
PATH=Z:\apps\git176\bin;...
Z:\apps\git176\bin\git.exe
 with param  origin/master
Z:\apps\git176\bin\git.exe
# On branch master
nothing to commit (working directory clean)
 with param
Z:\apps\git176\bin\git.exe
# On branch master
nothing to commit (working directory clean)

    So it seems to work. (As pointed out by Magnus, I don’t use exit)

    • 0