alt Hacker News> Several commands share names with built-ins in CMD and PowerShell. Whether the Coreutils version runs depends on the shell, the PATH order, and (for PowerShell) the alias table.
Well this is not very satisfying, what about proving a way where it actually works without us having to guess where the failure root cause happens to be?
Replies
How do you propose for this to be solved without breaking existing CMD batch files and PowerShell scripts and invocations by applications?
Maybe it’s for the llm tool use PATH?
That was the most plausible reason to even mention it, that I could think of.
The best part is the reason it conflicts with a lot of PowerShell is PowerShell shimmed Linux commands over to their Windows equivalents for years even though the flags were different.
So ls in many systems will match the behavior of dir, and only accept the flags for dir. But if you use a system with the newer coreutils release here, ls will expect ls flags!
Fully-qualify the path to the target program, and it should be no concern.