Package Details: zed-editor 0.134.2-1

Git Clone URL: https://aur.archlinux.org/zed-editor.git (read-only, click to copy)
Package Base: zed-editor
Description: A high-performance, multiplayer code editor from the creators of Atom and Tree-sitter
Upstream URL: https://zed.dev
Licenses: Apache-2.0, GPL-3.0-or-later, AGPL-3.0-or-later
Submitter: alerque
Maintainer: alerque
Last Packager: alerque
Votes: 32
Popularity: 11.62
First Submitted: 2024-01-24 19:09 (UTC)
Last Updated: 2024-05-08 17:09 (UTC)

Dependencies (25)

Required by (0)

Sources (2)

Pinned Comments

alerque commented on 2024-03-07 10:09 (UTC)

This package now builds and runs (at least in a clean chroot), so I'm setting pkgrel=1.

That being said there are still issues. Upstream support for Linux is not complete.

  • The generated binary is 800MB+. For some reason debug builds are only 400BM+.
  • Creating windows like file open dialogues is not working yet.
  • Surely more....

Please watch the upstream tracking issue for official news on Linux support.

As soon as Linux support is official and the editor handles basic functions like opening a project saving edited files I'll get it migrated to [extra].

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

alerque commented on 2024-02-18 08:47 (UTC)

So one thing we might be facing here is the need to un-vendor some stuff. Upstream has used some vendored dependencies and in one case it looks like maybe their own fork at that. I'm going to remove some of the dependencies that they are not claiming in their own CI builds and see where that gets us for a while. When things build the way they are "recommending", then we'll look deeper into how to unvendor things to be closer to Arch Linux guidelines.

alerque commented on 2024-02-18 07:24 (UTC)

@AAXZX Yes that is where the chroot dependencies are currently stuck at. Contributions welcome if you figure out the necessary incantation to get past that. It looks like it should be possible now, but I haven't figured out how.

AAXZX commented on 2024-02-14 00:34 (UTC) (edited on 2024-02-14 00:36 (UTC) by AAXZX) 

Caused by:
  process didn't exit successfully: `~/.cache/yay/zed-editor/src/zed-0.121.5/target/debug/build/live_kit_server-456cb40f6ab204fb/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at crates/live_kit_server/build.rs:4:10:
  called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "protoc failed: Could not make proto path relative: protocol/livekit_room.proto: No such file or directory\n" }

vpd commented on 2024-02-07 05:41 (UTC)

@alerque I'm on Arch Linux. I meant to say the build script looks for an Objective C header file on a Mac OS system yet I'm on Linux. Let me edit my comment to make this clear. Sorry for the confusion.

jvybihal commented on 2024-02-06 19:56 (UTC)

Thanks for the package. Now I've read the comments. Sorry for flagging the package out of date which was probably not neccesary.

UnityTheMaker commented on 2024-01-30 10:55 (UTC)

You can track the progress of Linux support here: https://github.com/zed-industries/zed/issues/7015

xolvum commented on 2024-01-30 09:31 (UTC)

i am using EndevourOS and i used yay and i am having this error 

 --- stderr
  thread 'main' panicked at crates/gpui/build.rs:122:10:
  called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: zed-editor-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
zed-editor - exit status 4

alerque commented on 2024-01-30 09:00 (UTC)

@vpd and anyone else actually on macOS. I don't know how you'd even be building this from a PKGBUILD without an Arch Linux environment, but I'm happy to accommodate anything if there is a way to fix it to build there.

Still watching upstream and will keep adapting this as they make any relevant build system changes for Linux. It looks like this is the issue to follow for now.

Mr.Smith1974 commented on 2024-01-28 10:50 (UTC)

Thanks for the package.

vkill commented on 2024-01-28 08:53 (UTC)

Thanks for the package.

« First ‹ Previous 1 2 3 4 5 Next › Last »