Question: How to fix "find: ‘\\cmd\\git.exe’: No such file or directory"?

[d4k0]

Question

Hi,

I just updated to 1.3.20 and now I get the message "find: ‘\cmd\git.exe’: No such file or directory" every time I start Cmder. I also tried a fresh portable installation, but the same thing is observed there. Is this a bug?

Checklist

• I have read the documentation and made sure what I'm looking for isn't present, or is unclear.
• I have searched for similar issues, and either this question wasn't asked before, or I didn't find any that describe my question.

[DRSDavidSoft]

Hi there, thanks for reporting this issue.

This is related to the following line of code:

cmder/vendor/init.bat

Line 244 in 2acb680

for /F "delims=" %%F in ('where git.exe 2^>nul ^| find "\cmd\git.exe"') do (

I'm not sure specifically why updating Cmder to 1.3.20 caused this issue, but the reason is because the unix find.exe is overwriting the windows find.exe in PATH, and since they do completely different things (one finds a file and the other finds a substring in text) they are not compatible.

I'll work on a fix right away, but in the meantime please open Command Prompt, cd to cmder root and try this command to see if the issue is resolved:

vendor\init.bat /nix_tools 0

if so, I'll make an update to the project that will resolve this issue. You'll need to download only the vendor\init.bat file from GitHub and replace it in your Cmder directory.

Thanks! 😄

[DRSDavidSoft]

Added a workaround in 8b6d1d8

@daxgames Can you please have a look and test?

[d4k0]

@DRSDavidSoft
Thanks for the quick answer. Unfortunately, that doesn't seem to have worked:

[daxgames]

@DRSDavidSoft 👍

Simple fully qualified path to find like %windir%\system32\find ..... would have worked too and may have been easier write and follow. :-)

[DRSDavidSoft]

@daxgames Ok, should I revert to using find.exe instead, with the fully qualified path?

This was meant to not rely on using external executables, which could potentially slow down the init process.

[chrisant996]

This line in the commit looks like it will fail when %full_path% contains spaces:

if not [\%full_path:\cmd\git.exe=:%]==[\%full_path%] (

@daxgames Ok, should I revert to using find.exe instead, with the fully qualified path?

This was meant to not rely on using external executables, which could potentially slow down the init process.

The fewer external executables and call commands, the better!!! Both of those can significantly slow down the init process.

[DRSDavidSoft]

@chrisant996 I just did a test and it seems that due to using double quotes, the space might not be an issue:

@echo off

setlocal enabledelayedexpansion

for /F "delims=" %%F in ('where code.cmd 2^>nul') do call :check_code "%%~fF"

:check_code
    set full_path="%~f1"
    if not defined CODE_INSTALL_ROOT (
        if not [\%full_path:\bin\code.cmd=:%]==[\%full_path%] (
            echo Executing "%~df1" --version
            "%~df1" --version
        )
    ) else (
        echo Skipping %full_path%
    )
    exit /b

Executing "C:\Program Files\Microsoft VS Code\bin\code.cmd" --version
1.70.2
e4503b30fc78200f846c62cf8091b76ff5547662
x64

In any case, I'm wondering which route is the better way to go, using a call :sub_routine to check substrings with if and string substitution, or using find.exe (with the fully qualified path) to filter out lines, and not use a subroutine.

Please feel free to do some tests and use the method that suits best. Thanks! 😄

[DRSDavidSoft]

@d4k0 Please follow these steps to see if the issue is resolved:

1. Open the Cmder that you've downloaded
2. Paste this command in full:

curl "https://raw.githubusercontent.com/cmderdev/cmder/master/vendor/init.bat" > %CMDER_ROOT%\vendor\init.bat

3. Wait for the command to finish, and take a screenshot so you can post it here
4. Exit Cmder then Restart it
5. Check if the issue persists.

Please report back if this solves the issue.

[chrisant996]

@chrisant996 I just did a test and it seems that due to using double quotes, the space might not be an issue:

...
    set full_path="%~f1"
...

I see now. I hadn't looked closely enough. Out of curiosity, what is the reason for the surrounding [..]? Since %full_path% already contains quotes, the \ before the %full_path% on each side looks like there isn't a functional need for the [..], and I made a bad assumption that they were meant to function similar to quotes. But 2 lines earlier there are clearly quotes, I just didn't look far enough, sorry!

[DRSDavidSoft]

The brackets were used mainly for two reasons:

1. Avoid an issue where an empty string would fail the comparison
2. Better code readability

However, I guess using the \ prefix invalidates both reasons, so I'll remove them.

Thanks for taking a closer look!

[296951]

@DRSDavidSoft No your fix is better. I am the lazy one!

[d4k0]

@DRSDavidSoft
Unfortunately, the issue persists:

After the restart of Cmder:

[chrisant996]

@DRSDavidSoft @daxgames another option could be to use findstr instead of find. The init.bat file already uses findstr elsewhere.

[chrisant996]

@dk40 The find program is no longer used in the latest init.bat file, so if you're still getting the same error then you don't have the fix yet.

Comment #2766 (comment) suggests how to download the latest init.bat file for testing purposes.