Search Issue Tracker
Duplicate
Votes
0
Found in
2017.2.0f3
Issue ID
973308
Regression
No
[UnityYAMLMerge] YAMLMerge does not work with external tools that take switchs with slashes on windows 10 creators fall update
UnityYAMLMerge tool does not work with external tools that take switchs with slashes on windows 10 creators fall update
I'm trying to get WinMerge to work with UnityYAMLMerge by adding the following line to mergespecfile.txt
- use "%programs%\WinMerge\WinMergeU.exe" /e "%r" "%l" "%d"
However when WinMerge is launched the command line looks like this in Process Explorer
C:\Program Files (x86)\WinMerge\WinMergeU.exe" \e "C:\Users\dkhje1\AppData\Local\Temp\MER79A.tmp" "C:\Users\dkhje1\AppData\Local\Temp\MER798.tmp" "C:\Users\dkhje1\AppData\Local\Temp\MER856.tmp
Which seems right but WinMerge will complain that the left file path is wrong and print it as "D:/e"
Same thing happens if I try unsing the predefined Araxis Merge which also uses slash switches except it will complain that both left and right files are wrong and show "D:/3" "D:/a2"
I produced the error trying to merge the two conflicting commits in the provided Mercurial repository using tortoiseHG
FIX
Update the mergespecfile.txt entry for WinMerge to the following:
- use "%programs%\WinMerge\WinMergeU.exe" -e "%r" "%l" "%d"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
This is a duplicate of issue #906354