Replies: 2 comments
-
If we were using a WSL Unix approximation of a Windows file name, then sure, the mapping DEVICE: to /mnt/DEVICE/path1/path2/file would probably be the right thing, otherwise if the code were compiled for the Windows interfaces which have a drive letter, then we should consider what to do with it. I don't know if we're going to run in pure Windows mode, though. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Going to transfer this to a Discussion about windows without X |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
... and when you had a colon in the name NOT as part of a device it confused the parser.
When you're running on a Windows system, host {dsk} should have a device -- "{dsk}D:/foo/bar.txt" would be the way I would expect to refer to a directory on the D: drive.
Originally posted by @nbriggs in #651 (comment)
Under WSL we could map the drive letters or "device" for remote mounts
{DSK}C:/path1/path2/file => /mnt/c/path1/path2/file
Beta Was this translation helpful? Give feedback.
All reactions