Skip to content

Conversation

@vkibalyuk
Copy link

No description provided.

@MrSubidubi
Copy link

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
Copy link

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

@MrSubidubi
Copy link

@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
Copy link

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

@MrSubidubi
Copy link

@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
Copy link

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

@yooakim
Copy link

yooakim commented Oct 29, 2025

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

@Dakota-LM
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants