Closed eggbean closed 8 months ago
Excuse me, I figured it out. I knew this before, but I forgot that this happens. There is some sort of issue where Windows .exe executables become unavailable within WSL when another instance of WSL has been opened in another local user account.
I must have had this working before, as it part of my automated WSL setup, but when I try using
xdg-open
to open anything in WSL, I get this error:The path is correct. The executable is there. What's happening?
The file is curled directly to
/usr/local/bin/xdg-open
and made executable.