Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.
Sign up to join this community
I installed cmder shell emulator for Windows.
Works fine but I can't use Unix's find command. Apparently when I type:
'find .'
in the terminal it tries to use the Windows' FIND and output this error:
FIND: Parameter format not correct
I'd really like to use find, any hint on how to get it working?
Simplest solution is to create an alias to the find executable within the cmder installation folder:
λ which find
/c/WINDOWS/system32/find
λ find --help
FIND: FIND: Parameter format not correct
λ alias find=C:\Files\Programs\cmder\vendor\git-for-windows\usr\bin\find.exe $*
λ find --help
Usage: /usr/bin/find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]
May I suggest you also try out Cygwin where, among other things, find works out of the box. That is what I used to ascertain the location of the cmder-supplied find.exe.
Kudos to @Bob and @AFH for their insightful comments, and to @Lưu Vĩnh Phúc for suggesting another dead-simple solution:
rename the *nix
findto another name likefnd.exe
This might actually be preferrable over creating an alias, because cmder aliases don't work in Windows 10 unless Use legacy console is selected in cmd properties (see how to do it).
cmder has the obvious advantage of being portable and not needing installation to be performed by a privileged user.
– simlev
Jun 14 '17 at 15:39
Cmder\vendor\git-for-windows\usr\bin is added to the PATH by Cmder\vendor\init.bat. Unfortunately, it's added at the end of the PATH, so Windows's find.exe is found first.
Fortunately, it's easy to fix. Just add this line inside Cmder\config\user-profile.cmd:
set "PATH=%GIT_INSTALL_ROOT%\usr\bin;%PATH%"
I have installed smartgit in windows
Then I add C:\Program Files (x86)\SmartGit\git\bin (my smartgit folder) into path environment
press win+r enter bash. in the bash shell you can use find command. in Cmder you also can type bash to use it
findis in appear beforeC:\Windows\System32(where Windows' find lives) in thePATHenvironment variable. This is generally considered not a great idea to do globally as it tends to confuse other programs that expect a standard Windows environment. Rather, you should see if you can set a startup script in Cmder, and make the script do something likeset PATH=C:\path\to\folder\with\unix\find;%PATH%– Bob Jun 14 '17 at 10:15cmder, but in Linux/Unixwhich -a findwill show all programs which could execute with the find command. Identify the Unixfind. Then use its full path, or re-arrange the order ofPATHdirectories, or set an alias, ifcmdersupports this; you could also rename the Windowsfind.exetowfind.exe. If it emulatesbash, then you can use the in-builttype -a find. – AFH Jun 14 '17 at 10:20sfc /scannowcan revert it – phuclv Jun 14 '17 at 16:28which -a findreturns/c/WINDOWS/system32/find /usr/bin/find. Unfortunately, though, running/usr/bin/findyieldsThe system cannot find the path specified.. It seems the actual windows-style path is needed here. Runningtypelaunches the windowstype, and it appearscmderdoes not provide the unix-like version. – simlev Jun 15 '17 at 8:15