Open krader1961 opened 2 years ago
I should point out that installing the Elvish binary as c:\msys64\usr\local\bin\elvish.exe
"fixes" the problem but it seems to me that a) shouldn't be necessary and b) if it is necessary then executing c:\msys64\usr\local\bin\elvish.
should not work if a binary with that name without an explicit exe
extension exists.
This issue is to remind me (or someone else) that there are quirks that need to be fixed regarding external command resolution on MS Windows. I made some upgrades to my Windows 10 system recently, including the Elvish version, which broke something that used to work.
The following interactive session capture shows several problems. Such as ANSI escape sequences being shown rather than acted on. For the purposes of this issue the problem is that an Elvish binary named
elvish
(no extension) is not recognized unless an explicit period is appended to the command name. That iselvish.
works whileelvish
does not but only if an absolute path is used. A bare command that relies on resolution via the$paths
list does not work the same way.