Remove redundant slash at the start of the path on Windows

[vkibalyuk]

No description provided.

[MrSubidubi]

I think this should not be needed anymore/the error should have been solved on the Zed side of things. Are you still running into the issue?

[ChaseBrand]

Can confirm this behavior on Windows and that this fork fixes it.

[MrSubidubi]

@ChaseBrand Are you on the latest Zed version?

In any case, the workaround should not be needed anymore. You should perhaps use env::current_dir() instead of path::absolute for this to be properly working, as then the workaround would not be needed anymore.

We did some work that should remove the need for such workarounds, hence it would be interesting to know whether using env::current_dir() solves the issue entirely or whether there is more to do.

[ChaseBrand]

@MrSubidubi I am on the Windows beta, so I would assume so. It updated this morning.

[MrSubidubi]

@ChaseBrand Well, I did forget an important part for this - the extension here would need to update the verison of the zed_extension_api to the latest version, so 0.0.7, in order for this to be fixed. Sorry...

[ask4fusora]

What's need to do next? Can I have an update.
Is there something blocking?

[yooakim]

I am on Zed nightly and I get this issuse. I installed the PowerShell extension today.

[Dakota-LM]

I'm on zed-preview and, yeah, still getting this initialization error

[lucaspimentel]

the extension here would need to update the verison of the zed_extension_api to the latest version, so 0.0.7, in order for this to be fixed.

I created a PR to update the zed_extension_api dependency in the extension: #28.

Cargo.toml:

[dependencies]
- zed_extension_api = "0.2.0"
+ zed_extension_api = "0.7.0"

I loaded my fork locally as a dev extension on Zed 0.216.1 and the PowerShell LS seems to load correctly now.