Forking to background when run from a terminal not reliably working on all Linuxes

[almereyda]

Often I run zed . in my source code repositories to get where I want.

On Ubuntu, this decouples the Zed process from the shell and forks it into the background/somewhere else.

On Fedora, the processe's stderr will be printed to the shell. Entering new commands is possible, but initiating Ctrl + C will stop the Zed progress.

What could I have done differently during the installation, in so these different behaviours appear?

Both were installed with the recommended installation method.

[bbb651]

Zed has two binaries, the editor itself and a cli, what's probably happening is that on fedora the zed in $PATH is the editor instead of the cli, so it's a packaging issue.

Both were installed with the recommended installation method.

How did you install on each system?

I think the only supported installation method is curl -f https://zed.dev/install.sh | sh, distribution packages are unofficial (not sure about flatpak, the manifest is here so it's technically official but the documentation makes it sound like it also has a lower level of support):

There are several third-party Zed packages for various Linux distributions and package managers, sometimes under zed-editor. You may be able to install Zed using these packages:

The fedora package seems to correctly use zed as the cli: https://github.com/terrapkg/packages/blob/286113193e51f9fd092b6bd9c732104d32b572ef/anda/devs/zed/stable/zed.spec#L77C1-L77C10 maybe you're using an old version? The official installation also works like this: 27beb9e

[almereyda]

Thanks for the hint. Both were installed with the piped script. On Ubuntu, zed --help reveals, that it's the CLI. Need to check on Fedora.