Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/flathub/dev.zed.zed
https://github.com/flathub/dev.zed.zed
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/flathub/dev.zed.zed
- Owner: flathub
- Created: 2024-07-28T18:32:41.000Z (5 months ago)
- Default Branch: master
- Last Pushed: 2024-10-23T20:24:43.000Z (2 months ago)
- Last Synced: 2024-10-24T08:02:53.596Z (2 months ago)
- Homepage: https://flathub.org/apps/details/dev.zed.Zed
- Size: 355 KB
- Stars: 10
- Watchers: 5
- Forks: 3
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Flatpak Zed
## Issues
Please open issues under: https://github.com/flathub/dev.zed.Zed/issues
## Usage
Zed's current Flatpak integration exits the sandbox on startup and most functionalities work out of the box. Workflows that rely on Flatpak's sandboxing may not work as expected by default.
Please note that Zed's flatpak still runs in an isolated environment and some language toolchains might misbehave when executed from the host OS into the sandbox.
To cope with it, Zed's flatpak defaults can be changed to:
- disable sandbox escape at startup
- enable SDK extensions to get support for additional languages
### Environment variables
- `ZED_FLATPAK_NO_ESCAPE`: disable flatpak sandbox escape (default: not set)
```shell
$ flatpak override --user dev.zed.Zed --env=ZED_FLATPAK_NO_ESCAPE=1
```
### Execute commands on the host system
When Zed's flatpak is running in the sandbox with no escape, it is not possible to execute commands on the host system.
To execute commands on the host system, run inside the sandbox:
```shell
$ flatpak-spawn --host
```
### SDK extensions
This flatpak provides a standard development environment (gcc, python, etc).
To see what's available:
```shell
$ flatpak run --command=sh dev.zed.Zed
$ ls /usr/bin (shared runtime)
$ ls /app/bin (bundled with this flatpak)
```
To get support for additional languages, you have to install SDK extensions, e.g.
```shell
$ flatpak install flathub org.freedesktop.Sdk.Extension.dotnet
$ flatpak install flathub org.freedesktop.Sdk.Extension.golang
```
To enable selected extensions, set `FLATPAK_ENABLE_SDK_EXT` environment variable
to a comma-separated list of extension names (name is ID portion after the last dot):
```shell
$ FLATPAK_ENABLE_SDK_EXT=dotnet,golang flatpak run dev.zed.Zed
```
To make this persistent, set the variable via flatpak override:
```shell
$ flatpak override --user dev.zed.Zed --env=FLATPAK_ENABLE_SDK_EXT="dotnet,golang"
```
You can use:
```shell
$ flatpak search
```
to find others.
### Run flatpak Zed from host terminal
If you want to run `zed /path/to/file` from the host terminal just add this
to your shell's rc file:
```shell
$ alias zed="flatpak run dev.zed.Zed"
```
then reload sources, now you could try:
```shell
$ zed /path/to/
# or
$ FLATPAK_ENABLE_SDK_EXT=dotnet,golang zed /path/to/
```
## Related Documentation
- https://zed.dev/docs/