Cannot access file:/// uri from WSL2

[edyu]

Please fill out the below information:

• Your Windows build number: (Type ver at a Windows Command Prompt)
  Microsoft Windows [Version 10.0.19025.1]

• What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
  when running commands in the shell that uses Start command.
  for example, I was running fish_config or help in the fish shell. Both of which use the Start command.
  For fish_config it calls
  Start file:///home/ed/.cache/fish/web_config-9S5EM8.html
  and for help it calls Start file:///usr/share/doc/fish/index.html

• What's wrong / what should be happening instead:
  The Linux path are not recognized in WSL. To make it easier to run commands in WSL2, I'd think all the Linux path should be recognized while in WSL2.
  Here are the commands and the errors:

~ fish_config                                                       
Web config started at 'file:///home/ed/.cache/fish/web_config-9S5EM8.html'. Hit enter to stop.
Start : This command cannot be run due to the error: The system
cannot find the file specified.
At line:1 char:1
+ Start "file:///home/ed/.cache/fish/web_config-9S5EM8.html"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Start-Process]     , InvalidOperationException
    + FullyQualifiedErrorId : InvalidOperationException,Microsoft.P     owerShell.Commands.StartProcessCommand

Shutting down.
 ~ help                                                   
Start : This command cannot be run due to the error: The system
cannot find the file specified.
At line:1 char:1
+ Start "file:///usr/share/doc/fish/index.html"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Start-Process]     , InvalidOperationException
    + FullyQualifiedErrorId : InvalidOperationException,Microsoft.P     owerShell.Commands.StartProcessCommand

[karuboniru]

So...you are calling PowerShell to open /hone/xxx by this?

$ powershell.exe start /home/xxx

That will not work, you need to use

$ powershell.exe start `wslpath -w '/home/xxx'`

or

$ powershell.exe start file://`wslpath -w '/home/xxx'`

Remember that you don't have /home for Windows programs.

You can hack xdg-open to do this convert. Write a "fake xdg-open" that converts linux path to Windows path and call powershell.exe start

[edyu]

I wasn't. This is mainly for fish shell. I'll inform them of this as well.