Why does @WSLPATH double the leading '/'?

[vefatica]

v:\> echo %@wslpath[infile]
//mnt/v/infile

Doubling the leading '/' doesn't hurt. Does it ever help?

 

[rconn]

/mnt/v/infile could be a valid Windows pathname. //mnt/v/infile isn't.

 

[vefatica]

/mnt/v/infile could be a valid Windows pathname. //mnt/v/infile isn't.

Thanks.

 

[AnrDaemon]

//mnt/v/infile isn't.

It is a valid UNC path.

 

[Alpengreis]

It is a valid UNC path.

//mnt/v/infile isn't under Windows ... only \\mnt\v\infile would be valid.

 

[vefatica]

/mnt/v/infile could be a valid Windows pathname. //mnt/v/infile isn't.

I don't see a difference in TCC. DIR and TYPE don't mind the extra leading slash.

v:\> dir "//mnt/v"

 Volume in drive V is DATA         Serial number is 6e8a:6d1f
 Directory of  V:\mnt\v\*

2019-10-22  12:15         <DIR>    .
2019-10-22  12:15         <DIR>    ..
2019-10-22  12:16               9  infile
                   9 bytes in 1 file and 2 dirs    4,096 bytes allocated
     506,830,897,152 bytes free

v:\> type "//mnt/v/infile"
3
2
1

 

[Alpengreis]

Oh, that's interesting ...

 

[AnrDaemon]

CMD is not an indication.
Try Win32 CreateFile directly.