-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running Zed through cargo run
or using a built release binary crashes immediately
#11319
Comments
cargo run
compiles zed but errors out when running Zedcargo run
or using a built release binary crashes immediately
The same thing happens to me but with Windows 10, everything compiled correctly, but when I run Zed.exe it throws this same error and does not open the application |
Hi, Since crucial functionality is not yet implemented for Linux and Windows (see here for Linux and here for Windows, the application cannot run in the first place. However, this logic is only invoked when the environment variable ZED_BUNDLE at compile time is set to true. (see here). As a workaround for now you can compile ZED on your own from source (without that environment variable) |
afaik you can just clone the repo and cd into the scripts then run ./install.sh (I just did, and it installed it fine on Linux, looks like some recent merges added the linux bit to the install script. I did this and its now installed on system and i run it with zed-preview (working fine, with the occational hiccup) |
I just tried to use the install script, although, the url that it tries to curl from doesn't exist, that url being https://zed.dev/api/releases/preview/latest/zed-linux-x86_64.tar.gz (I found this out by doing bash -x install.sh) |
This seems to be a duplicate of another issue that's being actively discussed. Be sure to +👍 and add any missing information to the other thread. Duplicate of: |
Check for existing issues
Describe the bug / provide steps to reproduce it
cargo run
or run a built binaryEnvironment
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.Although I have no log file, here is the error from the run command
The text was updated successfully, but these errors were encountered: