Closed jstarks closed 3 years ago
I looked into this and it seems much less surprising.
Yori is using the paths specified in that error report to the API. I didn't debug into kernel, but moving C:\Users\jostarks\tmp\foo
to C:\Users\jostarks\tmp\bar\
at the NtSetInformationFile level will create a file.
CMD's behavior is a little different because it detects the trailing slash and appends the file name after it, so the API gets C:\Users\jostarks\tmp\bar\foo
, which gets a failure.
I changed this behavior in commit ae3889c62bfb47137a4f90fdd74638acb68c60ab .
However, because the API doesn't behave in the way you're expecting, I have to ask: which other commands should have this behavior?
This should be fixed in 1.50, released today. Please let me know if there are further related issues.
I typically write trailing slashes on directory names that are targets of move/copy to ensure that the target directory exists. To my surprise, yori's move ignores this:
copy gets this right: