In MSYS2, for the binary files in the folder /usr/bin, I find that I can call them by "name" or "name.exe". However, in the Windows file system, there are only binary files with "exe" extensions. The "ls" and "file" commands can output information of binary files without "exe" extensions, too. However, when I execute "ls /usr/bin", the output contains no files without "exe" extensions. So why the shell of MSYS2 can find binary files without "exe" extensions in the folder /usr/bin? It is all well under bash, but when using zsh, the tab-completion always suggests the "command" and the "command.exe", it's very annoying.
Asked
Active
Viewed 868 times
1 Answers
2
This issue is discussed in more detail on this page as the third to last item under Table of Contents:
It would be helpful though if someone on the MSYS2 team could produce a complete list of all the 'hacks' that they have implemented in order to bridge incompatibilities between the MSYS2 (POSIX emulation) and Windows native environments (e.g., file path mangling, .exe extension interpolation, symlink copying, etc.) and explain exactly how they work.
If this already exists somewhere, can someone point to its location?
Silver Zachara
- 123
StackExchanger
- 433
- 1
- 4
- 10