Can't use non C: Drive

[beckervincent]

The PowerShell language server fails to initialize when Zed is used on X: drive (In my case a Windows Dev Drive), throwing Cannot find drive. A drive with the name '\C' does not exist error. The extension appears to incorrectly reference the C: drive regardless of the actual working directory?, i think.

initializing server powershell-es, id 22: Server reset the connection
-- stderr --
�[31;1mImport-Module: �[31;1mCannot find drive. A drive with the name '\C' does not exist.�[0m
�[31;1mStart-EditorServices: �[31;1mThe term 'Start-EditorServices' is not recognized as a name of a cmdlet, function, script file, or executable program.�[0m
�[31;1m�[31;1mCheck the spelling of the name, or if a path was included, verify that the path is correct and try again.�[0m

[aloneguid]

Same. My code is on ReFS with different drive letter.

[corbob]

I don't think this error is related to the path you're on, I think it is the extension itself not handling Windows paths. I've tested this on a VM with a single drive, and get the same error. I suspect (although have not tried), that if zed installed in WSL, and launched from there, then it might work... At least, I believe WSL maps the drives to the likes of /C...

[corbob]

Actually, I think this is a duplicate of #16 There also appears to be a workaround in the comments that seems to work, at least it did for me once I sorted out the paths in the settings.json that were slightly different for me.