Zed - Revision history

Linusemr618: Add GitHub Copilot issues to /* Troubleshooting */

2026-05-27T13:30:22Z

Add GitHub Copilot issues to Troubleshooting

@@ Line 435: / Line 435: @@
 <!--T:41-->
 When Zed reports missing tools, add the required executables to <code>programs.zed-editor.extraPackages</code> or wrap the server using <code>pkgs.writeShellApplication</code>.
 </translate>

Ekonovalov: fix typo in the option's name

2025-11-23T13:09:31Z

fix typo in the option's name

← Older revision		Revision as of 13:09, 23 November 2025
Line 274:		Line 274:

	<!--T:19-->		<!--T:19-->
	The <code>userSettings</code> and <code>~~userKeyMaps~~</code> options translate directly into JSON. The <code>extraPackages</code> option includes additional Nixpkgs in the FHS environment, useful for LSP servers (e.g., <code>pkgs.nixd</code>) or optional tools (e.g., <code>pkgs.shellcheck</code> for the Basher LSP).		The <code>userSettings</code> and <code>userKeymaps</code> options translate directly into JSON. The <code>extraPackages</code> option includes additional Nixpkgs in the FHS environment, useful for LSP servers (e.g., <code>pkgs.nixd</code>) or optional tools (e.g., <code>pkgs.shellcheck</code> for the Basher LSP).

	<!--T:20-->		<!--T:20-->

Ardenet: Marked this version for translation

2025-11-20T16:18:27Z

Marked this version for translation

← Older revision		Revision as of 16:18, 20 November 2025
Line 33:		Line 33:
	=== Imperative === <!--T:4-->		=== Imperative === <!--T:4-->

	==== Zed's Flake ====		==== Zed's Flake ==== <!--T:45-->
	</translate>		</translate>

Ardenet at 16:16, 20 November 2025

2025-11-20T16:16:07Z

← Older revision		Revision as of 16:16, 20 November 2025
Line 23:		Line 23:
	The editor provides native builds for Linux, including Nixpkgs packages and a reproducible flake. Hardware acceleration requires a GPU with Vulkan support; systems without Vulkan can fall back to emulation via tools such as [https://github.com/nix-community/nixGL nixGL].<ref>Zed Industries, "Linux", Zed Documentation, Accessed October 2025. https://zed.dev/docs/linux</ref>		The editor provides native builds for Linux, including Nixpkgs packages and a reproducible flake. Hardware acceleration requires a GPU with Vulkan support; systems without Vulkan can fall back to emulation via tools such as [https://github.com/nix-community/nixGL nixGL].<ref>Zed Industries, "Linux", Zed Documentation, Accessed October 2025. https://zed.dev/docs/linux</ref>

	{{Nixpkg\|pkgs/by-name/ze/zed-editor\|zed-editor}} is available in Nixpkgs since 24.11;		<!--T:5-->
	However, Zed provides [https://github.com/zed-industries/zed/blob/main/flake.nix an official nix flake] which might be useful if you need features that have not yet reached unstable Nixpkgs.		{{Nixpkg\|pkgs/by-name/ze/zed-editor\|zed-editor}} is available in Nixpkgs since 24.11; However, Zed provides [https://github.com/zed-industries/zed/blob/main/flake.nix an official nix flake] which might be useful if you need features that have not yet reached unstable Nixpkgs.

	== Installation == <!--T:3-->		== Installation == <!--T:3-->

			<!--T:6-->
	The package installs both desktop launchers and a CLI entry point aliased to <code>zeditor</code>, mirroring the upstream binary name		The package installs both desktop launchers and a CLI entry point aliased to <code>zeditor</code>, mirroring the upstream binary name

Line 99:		Line 100:
	Build the flake package with <code>nix build .#zed-latest</code> or expose it in your configuration with the appropriate overlay.		Build the flake package with <code>nix build .#zed-latest</code> or expose it in your configuration with the appropriate overlay.

			<!--T:12-->
	{{Warning\|Zed requires hardware-accelerated Vulkan. On systems without supported drivers, use <code>nixGL</code> or home-manager's <code>nixGL.vulkan.enable {{=}} true;</code> to provide the necessary libraries.		{{Warning\|Zed requires hardware-accelerated Vulkan. On systems without supported drivers, use <code>nixGL</code> or home-manager's <code>nixGL.vulkan.enable {{=}} true;</code> to provide the necessary libraries.
	Providing Vulkan through <code>nixGL</code> can be more consistent than relying on host distribution packages, especially on non-NixOS systems where Wayland and X11 stacks differ in their Vulkan capabilities.}}		Providing Vulkan through <code>nixGL</code> can be more consistent than relying on host distribution packages, especially on non-NixOS systems where Wayland and X11 stacks differ in their Vulkan capabilities.}}

Malix: enhancements: formatting, structure, simplification

2025-11-17T18:29:09Z

enhancements: formatting, structure, simplification

← Older revision		Revision as of 18:29, 17 November 2025
Line 19:		Line 19:
	<!--T:1-->		<!--T:1-->
	[https://zed.dev Zed]<ref>Zed Industries, "Zed", Official Website, Accessed October 2025. https://zed.dev</ref> is a collaborative, GPU-accelerated text editor developed by Zed Industries. It combines fast local editing with real-time multiplayer features and ships with batteries-included tooling for popular programming languages.		[https://zed.dev Zed]<ref>Zed Industries, "Zed", Official Website, Accessed October 2025. https://zed.dev</ref> is a collaborative, GPU-accelerated text editor developed by Zed Industries. It combines fast local editing with real-time multiplayer features and ships with batteries-included tooling for popular programming languages.
	~~</translate>~~
	~~<translate>~~
	<!--T:2-->		<!--T:2-->
	The editor provides native builds for Linux, including Nixpkgs packages and a reproducible flake. Hardware acceleration requires a GPU with Vulkan support; systems without Vulkan can fall back to emulation via tools such as [https://github.com/nix-community/nixGL nixGL].<ref>Zed Industries, "Linux", Zed Documentation, Accessed October 2025. https://zed.dev/docs/linux</ref>		The editor provides native builds for Linux, including Nixpkgs packages and a reproducible flake. Hardware acceleration requires a GPU with Vulkan support; systems without Vulkan can fall back to emulation via tools such as [https://github.com/nix-community/nixGL nixGL].<ref>Zed Industries, "Linux", Zed Documentation, Accessed October 2025. https://zed.dev/docs/linux</ref>
	~~</translate>~~

	~~<translate>~~		{{Nixpkg\|pkgs/by-name/ze/zed-editor\|zed-editor}} is available in Nixpkgs since 24.11;
			However, Zed provides [https://github.com/zed-industries/zed/blob/main/flake.nix an official nix flake] which might be useful if you need features that have not yet reached unstable Nixpkgs.

	== Installation == <!--T:3-->		== Installation == <!--T:3-->

	===~~= Shell =~~=== <!--T:4-->		The package installs both desktop launchers and a CLI entry point aliased to <code>zeditor</code>, mirroring the upstream binary name

			=== Imperative === <!--T:4-->

			==== Zed's Flake ====
	</translate>		</translate>

Line 35:		Line 39:
	</syntaxhighlight>		</syntaxhighlight>

	~~<translate>~~		==== Nixpkgs ====
	~~<!--T:5-->~~
	~~The <code>zed-editor</code> package is available in~~ Nixpkgs ~~from channel 24.11 onward. The command above provides <code>zed-editor</code> in the current shell session without modifying any configuration files.~~

	<~~!--T:6-~~->		<syntaxhighlight lang="console">
	~~The package installs both desktop launchers and a CLI entry point aliased to <code>zeditor~~</~~code~~>~~, mirroring the upstream binary name.~~		nix run nixpkgs#zed-editor
			</syntaxhighlight>

	===~~= System setup =~~=== <!--T:7-->		<translate>
			=== Declarative === <!--T:7-->
	</translate>		</translate>

			==== NixOS ====

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	~~# In /etc/nixos/configuration.nix~~
	environment.systemPackages = [		environment.systemPackages = [
	pkgs.zed-editor		pkgs.zed-editor
	];		];
			</syntaxhighlight>

			{{Evaluate}}
			==== Home Manager ====

	~~# In home-manager configuration (home.~~nix)		<syntaxhighlight lang="nix">
	home.packages = [		home.packages = [
	pkgs.zed-editor		pkgs.zed-editor
	];		];
			</syntaxhighlight>

			<syntaxhighlight lang="console">
			home-manager switch
	</syntaxhighlight>		</syntaxhighlight>

	<translate>		<translate>
	~~<!--T:8-->~~		==== Zed's Flake ==== <!--T:9-->
	~~Rebuild your system or Home Manager profile to make Zed available persistently. On NixOS, run <code>sudo nixos-rebuild switch</code>; for Home Manager, run <code>home-manager switch</code>.~~

	==== Flake ==== <!--T:9-->

	~~<!--T:10-->~~
	~~Zed maintains an official flake for tracking the latest upstream build. This approach is useful if you need features that have not yet reached stable Nixpkgs.~~
	</translate>		</translate>

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	inputs.zed.url = "github:zed-industries/zed";		{
			inputs.zed.url = "github:zed-industries/zed";

	outputs = { self, nixpkgs, zed, ... }@inputs: let		outputs =
	system = "x86_64-linux";		{
	pkgs = import nixpkgs { inherit system; };		self,
	in {		nixpkgs,
	packages.${system}.zed-latest = zed.packages.${system}.default;		zed,
	};		...
			}@inputs:
			let
			system = "x86_64-linux";
			pkgs = import nixpkgs { inherit system; };
			in
			{
			packages.${system}.zed-latest = zed.packages.${system}.default;
			};
			}
	</syntaxhighlight>		</syntaxhighlight>

Line 81:		Line 98:
	<!--T:11-->		<!--T:11-->
	Build the flake package with <code>nix build .#zed-latest</code> or expose it in your configuration with the appropriate overlay.		Build the flake package with <code>nix build .#zed-latest</code> or expose it in your configuration with the appropriate overlay.
	~~</translate>~~
	{{Warning\|Zed requires hardware-accelerated Vulkan. On systems without supported drivers, use <code>nixGL</code> or home-manager's <code>nixGL.vulkan.enable {{=}} true;</code> to provide the necessary libraries.}}		{{Warning\|Zed requires hardware-accelerated Vulkan. On systems without supported drivers, use <code>nixGL</code> or home-manager's <code>nixGL.vulkan.enable {{=}} true;</code> to provide the necessary libraries.
	~~<translate>~~		Providing Vulkan through <code>nixGL</code> can be more consistent than relying on host distribution packages, especially on non-NixOS systems where Wayland and X11 stacks differ in their Vulkan capabilities.}}
	~~<!--T:12-->~~
	Providing Vulkan through <code>nixGL</code> can be more consistent than relying on host distribution packages, especially on non-NixOS systems where Wayland and X11 stacks differ in their Vulkan capabilities.

	== Configuration == <!--T:13-->		== Configuration == <!--T:13-->

Malix: update, format, use native features

2025-11-17T16:50:16Z

update, format, use native features

Show changes

Merrkry: /* LSP support */

2025-11-03T13:22:30Z

LSP support

← Older revision		Revision as of 13:22, 3 November 2025
Line 252:		Line 252:
	<translate>		<translate>
	<!--T:22-->		<!--T:22-->
	Zed downloads ~~language~~ servers into <code>~/.local/share/zed/languages/</code>~~, which is read-only on NixOS~~. ~~Instead, use declarative~~ methods ~~to supply~~ LSP ~~binaries~~.		Zed downloads LSP servers into <code>~/.local/share/zed/languages/</code>. These binaries most likely will not work because of linking issues. You can workaround this with the following methods or bring your own LSP servers.
	</translate>		</translate>
	<translate>		<translate>
	<!--T:23-->		<!--T:23-->
	Check <strong>LSP Logs → Server Info</strong> to confirm which binaries are running~~. Prefer language servers packaged in Nixpkgs so that dependencies are resolved within the Nix store~~.		Check <strong>LSP Logs → Server Info</strong> to confirm which binaries are running.
	</translate>		</translate>

Line 262:		Line 262:
	<translate>		<translate>
	<!--T:24-->		<!--T:24-->
	Enable [[FAQ#I've downloaded a binary, but I can't run it, what can I do?\|<code>nix-ld</code>]] so ~~prebuilt~~ language servers can resolve dynamic libraries without wrapping.		Enable [[FAQ#I've downloaded a binary, but I can't run it, what can I do?\|<code>programs.nix-ld</code>]] so language servers downloaded by Zed can resolve dynamic libraries without wrapping and work out of the box.
	</translate>		</translate>

Line 273:		Line 273:
	<translate>		<translate>
	<!--T:26-->		<!--T:26-->
	Remember that language servers started inside the wrapper do not ~~automatically~~ inherit tools from ad-~~hoc shells; include every dependency declaratively~~.		Remember that language servers started inside the wrapper do not inherit tools and libraries from nix shell. This is usually not desired because LSP may need project-level dependencies provided by nix-shell to compile and analyze the code.
	</translate>		</translate>

Line 303:		Line 303:
	Adjust the path for each language server you manage. The example above assumes rust-analyzer is installed in your system profile.		Adjust the path for each language server you manage. The example above assumes rust-analyzer is installed in your system profile.
	</translate>		</translate>

	== Remote server ==		== Remote server ==
	<translate>		<translate>

Layer-09 at 12:48, 17 October 2025

2025-10-17T12:48:28Z

Show changes

Layer-09: Formatting, translation tags, adherence to the manual

2025-10-17T12:31:33Z

Formatting, translation tags, adherence to the manual

Show changes

Jacobmichels: Format `zed` as code properly.

2025-10-15T02:33:36Z

Format `zed` as code properly.

← Older revision		Revision as of 02:33, 15 October 2025
Line 13:		Line 13:

	=== Flake ===		=== Flake ===
	Zed provides a flake at https://github.com/zed-industries/zed/blob/main/flake.nix. As `zed` updates frequently, you may prefer this option over nixpkgs.		Zed provides a flake at https://github.com/zed-industries/zed/blob/main/flake.nix. As <code>zed</code> updates frequently, you may prefer this option over nixpkgs.

	== LSP Support ==		== LSP Support ==