[Windows] path

[zaoqi]

run-pipeline: unix pipeline-segment (#<path:C:/Users/libre/scoop/apps/yarn/current/Yarn/bin\yarn>) terminated with code -1

[willghatch]

Interesting.

I'm not sure I fully understand what is going on here with that backslash. Can you give me the full command you used that gave this error? What do you get back when you run (find-executable-path "yarn") in Racket (or Rash)?

I'm traveling and busy for the next few weeks, so it may take me a while to get to this, unfortunately, but thank you for the report!

[zaoqi]

> (find-executable-path "yarn")
#<path:C:/Users/libre/scoop/apps/yarn/current/Yarn/bin\yarn>

[willghatch]

On Fri, Jun 14, 2019 at 10:11:32AM -0700, Zaoqi wrote: ``` > (find-executable-path "yarn") #<path:C:/Users/libre/scoop/apps/yarn/current/Yarn/bin\yarn> ```

This looks like a Racket bug. I'm guessing you get the same results with `(system* (find-executable-path "yarn"))` -- IE a bad return value because it can't actually run the program? (At least that's my interpretation of what this report means -- I'm not sure what a `-1` return on Windows means.) Is my interpretation here correct?

[zaoqi]

@willghatch
Windows seems to ignore \, so Windows thinks that path is C:/Users/libre/scoop/apps/yarn/current/Yarn/binyarn.

[willghatch]

So I'm finally home from travelling and I fired up a Windows machine to test this out.

I can construct paths that have a mix of forward and back slashes using build-path, and they aren't inherently broken. Normally Racket seems to handle them properly. For example, (build-path "C:/Windows/system32" "winver.exe") gives me #<path:C:/Windows/system32\winver.exe>, but that runs fine when I use it with system* or subprocess.

I see that with subprocess on Windows I do get a status of -1 when I try to run a nonexistent file OR a file that exists but isn't a proper executable. So I wonder if somehow find-executable-path may decide that a file is executable even if it's not actually executable on your machine. Is C:/Users/libre/scoop/apps/yarn/current/Yarn/bin\yarn a valid Windows executable? I would expect it to probably have .exe on windows. Perhaps there is just another file in the directory that has executable permissions on the file system but isn't valid for Windows?