[Bug] command such as `ls`、`grep`、`where` not found in bash

[zwyyy456]

Version Information

Cmder version: 1.3.25
Operating system: windows10 22h2

Cmder Edition

Cmder Full (with Git)

Description of the issue

I installed cmd-full by scoop. Then when I open cmder and use mitty or bash, it shows that bash: /c/Users/cffex/scoop/apps/cmder-full/current/vendor/git-for-windows/bin/cp: cannot execute: required file not found.

When I try to run ls, it shows that bash: /c/Users/cffex/scoop/apps/cmder-full/current/vendor/git-for-windows/bin/ls: cannot execute: required file not found. When I try /usr/bin/ls or /bin/ls, the command works, and when I try /usr/bin/ls /c/Users/cffex/scoop/apps/cmder-full/current/vendor/git-for-windows/bin, there
are lots of exe files such as ls.exe, but I can only find bash.exe and git.exe and sh.exe in windows file explorer.

When I try to run /usr/bin/which ls, it shows that /c/Users/cffex/scoop/apps/cmder-full/current/vendor/git-for-windows/bin/ls.

How can I fix this problem? I don't want to type /usr/bin/ls every time I want to use the ls command.

How to reproduce

No response

Additional context

No response

Checklist

• I have read the documentation.
• I have searched for similar issues and found none that describe my issue.
• I have reproduced the issue on the latest version of Cmder.
• I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.

[DRSDavidSoft]

Can you please check what is the contents of your PATH environment variable?

If it doesn't contain /usr/bin (sperated by colon), then something is causing it to be broken. You can add it back, but I believe it's important you find out what is exactly happening here. Did you install and/or configure anything else?

Please post the full contents of your PATH environment variable here. It is designed literally for what you're asking here.

In case that the variable DOES contain /usr/bin, but the ls command is not working, please type the following commands as well and post the results here:

type ls
which ls

The job of the commands above is to figure out which binaries are getting executed. In case you have multiple ls.exe files on your PATH, maybe you're executing one that has some potential problems.

---

Tip! In case you would like to easily search your system for multiple instances of a file with the same name, I recommend installing VoidTools' Everything Search and typing in for example (\ls.exs) in the search box to find the list of files with that name on your machine.

[zwyyy456]

Can you please check what is the contents of your PATH environment variable?

If it doesn't contain /usr/bin (sperated by colon), then something is causing it to be broken. You can add it back, but I believe it's important you find out what is exactly happening here. Did you install and/or configure anything else?

Please post the full contents of your PATH environment variable here. It is designed literally for what you're asking here.

In case that the variable DOES contain /usr/bin, but the ls command is not working, please type the following commands as well and post the results here:

type ls which ls

The job of the commands above is to figure out which binaries are getting executed. In case you have multiple ls.exe files on your PATH, maybe you're executing one that has some potential problems.

Tip! In case you would like to easily search your system for multiple instances of a file with the same name, I recommend installing VoidTools' Everything Search and typing in for example (\ls.exs) in the search box to find the list of files with that name on your machine.

[DRSDavidSoft]

Great thinking, I can see your PATH. Can you please also type this:

/usr/bin/cygpath -w /usr/bin

Lastly, try this. Type: PATH="/usr/bin:$PATH". Next, type some commands like ls to see what happens.

Using these two steps I might be able to identify your problem. Thanks for the help! 👍🏻

[zwyyy456]

Great thinking, I can see your PATH. Can you please also type this:

/usr/bin/cygpath -w /usr/bin

Lastly, try this. Type: PATH="/usr/bin:$PATH". Next, type some commands like ls to see what happens.

Using these two steps I might be able to identify your problem. Thanks for the help! 👍🏻

Sorry to be late, the output of /usr/bin/cygpath -w /usr/bin is C:\Users\cffex\scoop\apps\cmder-full\1.3.25\vendor\git-for-windows\usr\bin. After I run export PATH=/usr/bin:$PATH, ls works well.

[chrisant996]

The $PATH that was shared already contains /usr/bin:

So, maybe one of the directories earlier in the list has files that conflict and causing problems with launching programs.

The first directory in $PATH is /c/Users/cffex/bin which seems to be a custom directory that isn't part of Cmder, so maybe that could be worth investigating.

What is the output from /usr/bin/ls -a -F --color /c/Users/cffex/bin?

UPDATE:

Also, when I start the bash that comes with git, my $PATH is in a different order:

Maybe you have some customizations which have altered the normal $PATH in a way that's causing problems.

[zwyyy456]

The $PATH that was shared already contains /usr/bin:

So, maybe one of the directories _earlier_ in the list has files that conflict and causing problems with launching programs.

The first directory in $PATH is /c/Users/cffex/bin which seems to be a custom directory that isn't part of Cmder, so maybe that could be worth investigating.

What is the output from /usr/bin/ls -a -F --color /c/Users/cffex/bin?

UPDATE:

Also, when I start the bash that comes with git, my $PATH is in a different order:

Maybe you have some customizations which have altered the normal $PATH in a way that's causing problems.

I installed cmder-full by scoop, also I tried to download cmder-full manually, ls works well.

[zwyyy456]

/usr/bin/ls -a -F --color /c/Users/cffex/bin

The output of /usr/bin/ls -a -F --color /c/Users/cffex/bin is /usr/bin/ls: cannot access '/c/Users/cffex/bin': No such file or directory

[DexterWernJr]

1. ---