Unity plugin doesn't detect ZED Editor on Windows

[xchesh]

The Unity plugin doesn't find ZED Editor on Windows because there are no defined search paths for the Windows installation.

Expected Behavior
The plugin should detect and connect to ZED Editor automatically on Windows, just like it does on other platforms.

Steps to Reproduce

• Install ZED Editor on Windows.
• Open Unity with the ZED plugin installed.
• Try to open or connect to ZED Editor.
• Observe that the plugin doesn't detect ZED Editor.

Environment

• OS: Windows 10 / 11
• Unity: 6000 LTS+
• ZED Editor: Latest Windows version

@Maligan

[SuperJura]

I managed to get Discovery working, but there is something wrong in OpenProject function.

I didn't find Zed's documentation about opening files, no idea what '-a' does. If I remove '-a' parameter and call something like
zed "C:/UnityProjects/ZedDev" "C:\UnityProjects\ZedDev\Assets\unity-zed\Editor\ZedDiscovery.cs" it opens the file.
But I have no idea how to open on specific line nor column.

I'll try to get it working soon, but if anyone has some free time, here is the fork unity-zed-windows

[xchesh]

@SuperJura i think @Maligan can help us :)

[SuperJura]

great, if we fix this one bug, I think this is mergeable.

[Maligan]

Oh, sorry for late reply! I didn't notice Zed got window support!

@SuperJura thanks you for your fork, I've seen the code and will adapt the solution, or if you want you can make a PR

[SuperJura]

#12
Here is the PR

[ViggoLarsen]

@SuperJura the '-a' parameter isn't valid, but you can open a certain line and even column by appending :line:column, with your example that would be:

zed "C:/UnityProjects/ZedDev" "C:\UnityProjects\ZedDev\Assets\unity-zed\Editor\ZedDiscovery.cs:5"

[SuperJura]

@ViggoLarsen no idea, maybe I have some broken build installed, but this does not work for me

[Namey5]

I'm guessing this is a bug, but currently Zed.exe doesn't seem to properly support opening both a project and a file:line[:column] in a single command.

You can open a project to a specific file just fine:

Zed.exe Path\To\Project Path\To\Project\File.cs

But if you try that same command and specify a line:

Zed.exe Path\To\Project Path\To\Project\File.cs:127

Zed seems to treat it as opening an unrelated file from a different workspace, and instead adds it as an out-of-tree file.

As a workaround, opening the project first and then adding the file to it in an additional command seems to work:

Zed.exe Path\To\Project && Zed.exe -a Path\To\Project\File.cs:127

This might do something strange if you already have multiple projects open though.

[SuperJura]

Zed fixed their bugs, I made a fork based on this implementation with my own fixes and refactors if anyone is interested:
Unity Zed Integration