-
Notifications
You must be signed in to change notification settings - Fork 38
Add support for files whose canonical paths use UNC prefixes. #156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
On Windows, files on network shares have a canonical path which starts with the UNC "\\?\" prefix. With these prefixes, the OS no longer handles "." paths and trailing slashes, so handle them manually. Fixes #2650.
fa34d93 to
8893496
Compare
54edf80 to
91d3d4b
Compare
|
Looking at the test failures, this needs some more work before it's ready. |
91d3d4b to
a77b2e4
Compare
a77b2e4 to
2e51b7f
Compare
|
Windows has some functions which perform canonicalization. I've now submitted retep998/winapi-rs#992 to add bindings to these in winapi, so we can experiment with using those instead of trying to do the canonicalization manually. |
|
Another option is to use windows-rs. That seems like the next thing to try here. |
fc0ebc2 to
dd73714
Compare
4a03710 to
6e53944
Compare
windows-sys has bindings for `PathCchCanonicalizeEx`, `PathCchCombineEx`, and `PathCchAppendEx`, which we may be able to use in #156.
windows-sys has bindings for `PathCchCanonicalizeEx`, `PathCchCombineEx`, and `PathCchAppendEx`, which we may be able to use in #156.
|
A better path forward for this issue is to change cap-std to use |
On Windows, files on network shares have a canonical path which starts
with the UNC "\?" prefix. With these prefixes, the OS no longer
handles "." paths and trailing slashes, so handle them manually.
Fixes #2650.