input url will not invoke error which caused issue

[patrick330602]

Originally reoported on #243 and #244 (comment) by @crossing

wslpath -w is not return error for url now; instead, it throws a interesting badly encoded string like the following:

 $ wslpath -w https://google.com
https\google.com

[marveloo]

I think this behaviour of wslpath is intentional. I would guess this is related the fact that Windows does not support colon characters in file names, therefore, they translate colons into something else to maintain interoperability.

Example:

$ mkdir "https:"
$ echo "Hello!" > "https://google.com"
$ cat "https://google.com"
Hello!
$ notepad.exe "$(wslpath -w "https://google.com")"

Notepad opens the file with its contents just fine here.