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-03-20 17:02 (UTC) (edited on 2024-03-20 18:30 (UTC) by alerque)

As of v0.127.3 I'm going to start holding this packaging back to the stable channel. It has been on the *-pre series of tags up until now since at the beginning those were the only ones building at all, but now I think it's fair to start moving this slowing to shape for [extra]. It's actually behaving itself as an editor now, albeit with some rough edges still. If you want the pre-releases use zed-editor-preview, or for a bleeding-edge build you can use zed-editor-git.

If folks know of issues that are happening with this packaging that are overcomable using upstream code let me know (e.g. file pickers are still not working reliably. I think it is upstream, but if it was a dependency issue I'd be happy to be made aware...).

jsimon0 commented on 2024-03-19 12:30 (UTC)

Just as a note, beware before compiling this package. I know this is not really a packaging issue, but....it uses a ridiculous amount of RAM. 14-16GB at its peak. Have enough free RAM or sufficient swap beforehand.

alerque commented on 2024-03-19 12:13 (UTC)

@ashabayek and @damian101, please report runtime issues upstream, not here. This comment section should only be for issues with the packaging, not with Zed itself.

ashabayek commented on 2024-03-15 11:04 (UTC)

@damian101 same here, it was working fine prior to last update.

damian101 commented on 2024-03-15 11:00 (UTC)

It builds and installs, but I can only run it from terminal, where it quickly crashes:

❯ Zed
[2024-03-15T11:58:25+01:00 ERROR util] crates/settings/src/settings_file.rs:76: EOF while parsing a value at line 1 column 0
[2024-03-15T11:58:26+01:00 ERROR util] crates/zed/src/zed.rs:615: EOF while parsing a value at line 1 column 0
[2024-03-15T11:58:26+01:00 ERROR util] crates/zed/src/main.rs:694: No such file or directory (os error 2)
[2024-03-15T11:58:28+01:00 ERROR util] crates/zed/src/main.rs:994: Is a directory (os error 21)
[2024-03-15T11:58:28+01:00 ERROR Zed] {
  "thread": "main",
  "payload": "already borrowed: BorrowMutError",
  "location_data": {
    "file": "crates/gpui/src/platform/linux/wayland/client.rs",
    "line": 301
  },
  "backtrace": [
    "__libc_start_main"
  ],
  "app_version": "1.0.0",
  "release_channel": "Zed Preview",
  "os_name": "Linux",
  "os_version": "1.0.0",
  "architecture": "x86_64",
  "panicked_on": 1710500308618,
  "installation_id": "e90fd294-1974-42bd-a20d-5f41d3f21f43",
  "session_id": "38c329c4-dcc3-498a-a44d-497c2fcb52c9"
}

alerque commented on 2024-03-13 12:56 (UTC)

@grandchild, yes, the incorrect permissions were causing the automatic striping to fail (among other issues).

One other major current issue is the build seems to hard code some paths internally to itself and fails to run if built in a chroot. Contributions welcome if anybody figures out what files are/are not needed where or how to fix the path handling at build time.

In other news it seems possible we now have a few more dependencies than we actually need. Anybody with input on that front is welcome to contribute.

grandchild commented on 2024-03-12 13:59 (UTC)

@alerque your recent change to the permissions fixed the stripping of the binary. 0.126.2-1 has a 800+MiB binary, and the 0.126.2-2 binary is 155MiB. :+1:

alerque commented on 2024-03-12 11:26 (UTC)

@titaniumtown If you are not building in a chroot per Arch recommendations and you've changed your host system's makepkg defaults to use clang instead of gcc then yes that might fail ... and you're on your own for other things you have to adjust to make it work.

@grandchild The Arch package build system strips binaries by default.

titaniumtown commented on 2024-03-11 11:44 (UTC)

@alerque Maybe it was clang-related then?

grandchild commented on 2024-03-09 18:18 (UTC)

You can get the binary size down to 155MiB by simply stripping it.

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