GDQuest
Diagnostics does not appear in the current file, but it does appear in the multibuffer
https://github.com/user-attachments/assets/d2477194-ec90-4190-8bee-9a6555e3d873
Godot: 4.5.1 NMap: 7.98 Zed: v0.211.6 OS: Windows 10.0.26200
Do you have diagnostics enabled? Here:
I was able to reproduce this behavior when I disabled diagnostics. If they are are enabled for you and you still have this issue, it's probably a bug in Zed.
Hi @fstxz. Yes, the diagnostics are enabled and don't show up in the GDScript file, though I haven't tried with GDResource or GDShader. Maybe this is an OS specific problem, 'cause this doesn't occur on Linux.
Maybe this is an OS specific problem, 'cause this doesn't occur on Linux.
In this case I recommend opening an issue in the Zed repo (here). The extension doesn't do much by itself - it just connects Zed with Godot's LSP, everything else is handled by Zed and Godot. If the issue doesn't appear on Linux, then it's most likely a bug in the Windows version of Zed.
This won't be fixed on Zed's side, so I'm simply not going to use the symlinked folder. @fstxz, feel free to close this issue.
Thank you for following up on this and letting us know. Closing as this is outside of our control and it's been closed as not planned on Zed itself.
@NathanLovato would you mind keeping this open and tagging it as language server issue? From taking a brief read, I'd say the server should be transforming its response paths to the location which the client indicated when it initialized the connection. This is probably not done right now and should be fixable in the server.
@HolonProduction Sure! Thank you for looking into this, and for your work on the language server, it's much appreciated.