Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0f3
Issue ID
906354
Regression
No
[UnityYAMLMerge] UnityYAMLMerge changing forward slashes to backslashes for fallback tool arguments
UnityYAMLMerge changing forward slashes to backslashes for fallback tool arguments
UnityYAMLMerge is changing the forward slashes to backslashes in the fallback tool arguments, making some fallback tools to fail.
For example, I'm trying to use Visual Studio's vsdiffmerge.exe as a fallback tool, using this line in the file mergespecfile.txt:
* use "C:/Programas/Desarrollo/Visual Studio 2017/Common7/IDE/CommonExtensions/Microsoft/TeamFoundation/Team Explorer/vsdiffmerge.exe" /m "%r" "%l" "%b" "%d"
The "/m" argument makes vsdiffmerge launch the merge tool, instead of the diff tool. However, UnityYAMLMerge changes it to "\m", which makes the tool fail (or launch the diff tool if the argument is at the end).
https://answers.unity.com/questions/1327599/unity-smart-merge-unityyamlmergeexe-how-to-configu.html
https://forum.unity.com/threads/using-visualstudio-build-in-merge-tool-alongside-unityyamlmerge.350549/
-
EyePD
Aug 22, 2019 14:15
What is the status of the newly revamped merging system and where can I find more information? The 2019.2 Smart Merge documentation still references YAMLMerge so I'm assuming the new system is not yet completed.
-
AlanMattano
Apr 25, 2019 12:09
Can you add a worarround to : https://forum.unity.com/threads/bug-invalid-command-line-using-collaborate-and-winmerge.603064/#post-4468993
-
rastlin
Jul 16, 2018 16:50
Not sure why this is still not resolved.
A simple workaround is to create a bat file with the parameter hardcoded, and in mergespecfile reference said file instead of vsdiffmerge:
bat:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\vsdiffmerge.exe" "%1" "%2" "%3" "%4" /mmergespecfile:
* use "<PATH_TO_BAT_FILE>" "%l" "%r" "%b" "%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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.1.X):
Due to the age of this issue, and since YAMLMerge is in the process of being replaced by a newly revamped merging system, our team has decided to close this issue as Won't Fix.