You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launching Zed normally does not automatically load necessary LSPs for the project, but using zed [workspace] correctly loads the LSPs.
Steps to trigger the problem:
Install Zed.
Open Zed.
Install the Zed CLI via the menu.
Open any project with Zed (I've tried TypeScript projects with eslint/prettier/tailwind and a Go project).
Open a file and note that the primary LSP for the language (TypeScript or Go) does not load.
Close Zed.
Open a terminal.
Open the same project using zed [workspace].
Note that immediately upon the workspace loading, the LSP for the language (TypeScript or Go) is loaded.
Open a file and note that LSP features are enabled.
Actual Behavior:
Opening a file (not using the CLI) does not load the primary LSP for the language (TypeScript or Go) as soon as the workspace loads.
Expected Behavior:
Opening a file (not using the CLI) correctly loads the primary LSP for the language (TypeScript or Go) as soon as the workspace loads.
Summary
Launching Zed normally does not automatically load necessary LSPs for the project, but using
zed [workspace]
correctly loads the LSPs.Steps to trigger the problem:
zed [workspace]
.Actual Behavior:
Opening a file (not using the CLI) does not load the primary LSP for the language (TypeScript or Go) as soon as the workspace loads.
Expected Behavior:
Opening a file (not using the CLI) correctly loads the primary LSP for the language (TypeScript or Go) as soon as the workspace loads.
Zed Version and System Specs
Zed: v0.174.6 (Zed)
OS: macOS 15.3.1
Memory: 16 GiB
Architecture: aarch64
The text was updated successfully, but these errors were encountered: