Jason Edmeades jason@edmeades.me.uk writes:
move is not tollerent of the source and destination being the same and happily removes the destination (after prompting) ready to move the file, only to appear shocked that the file is no longer there...
This was sent originally where I compared filenames, and was given feedback to use a better system of equality. This now uses something the MSDN implies is the best way to tell for equivalent destinations
This should be done in MoveFile, and cmd should use that instead of duplicating the checks.
On Thu, Jun 13, 2013 at 12:23 PM, Alexandre Julliard julliard@winehq.org wrote:
Jason Edmeades jason@edmeades.me.uk writes:
move is not tollerent of the source and destination being the same and happily removes the destination (after prompting) ready to move the file, only to appear shocked that the file is no longer there...
This was sent originally where I compared filenames, and was given feedback to use a better system of equality. This now uses something the MSDN implies is the best way to tell for equivalent destinations
This should be done in MoveFile, and cmd should use that instead of duplicating the checks.
Then I think bug 14901 may be related. http://bugs.winehq.org/show_bug.cgi?id=14901
-- Alexandre Julliard julliard@winehq.org
Best wishes, Bruno