Use SDK with zed with escape option off

flathub / dev.zed.Zed

https://flathub.org/apps/details/dev.zed.Zed

9 stars 3 forks source link

Use SDK with zed with escape option off #6

Open baronleonardo opened 1 month ago

baronleonardo commented 1 month ago

I used this env ZED_FLATPAK_NO_ESCAPE=1 and FLATPAK_ENABLE_SDK_EXT=llvm15, but the later was never recognized (the terminal doesn't see clang at all)

appelgriebsch commented 1 month ago

I think we need a startup script that enables the SDK similar to this: https://github.com/Lctrs/jetbrains-flatpak-wrapper/blob/master/jetbrains.sh#L51-L74

jerome-benoit commented 1 week ago

flatpak override --user dev.zed.Zed --env=ZED_FLATPAK_NO_ESCAPE=1 should be enough to make it the default for your user.
The flatpak use your host runtime for LLVM version. If your distro is shipping several versions on LLVM, you should be able to configure any editor or build system to use the right one: llvm-*-\<version>.

baronleonardo commented 1 week ago

I don't want to use anything from my host I want to use the SDKs from flatpak

jerome-benoit commented 1 week ago

What is the detailed rationale for that usage?

baronleonardo commented 1 week ago

hmmm, that's how I develop, and that how I keep my system clean all the tools I need is withing flatpak, whatever it is a binary or sdk if I need an extra library, I simply compile it

jerome-benoit commented 1 week ago

It's a somewhat light rationale for a change that introduce serious downsides to the zed flatpak behavior (cf. follow up PR comments) by using existing tools ;-). Even if done without introducing breaking change. A proper integration would require to make a lighter zed dedicated wrapper.

baronleonardo commented 1 week ago

this is the same behavior I get from vscode, micro, vim, ... the only IDE/text editor I know that doesn't support it is zed and that is ok, it is still in the beginning of flatpak support anyway for me (at least) this is an important feature that prevent me from using zed

jerome-benoit commented 1 week ago

I doubt the maintainer will accept the PR with the current issues raised during testing (as a maintainer, I'll not). Integration is still doable but will need to implement a dedicated shell wrapper, and I do not have that time at the moment.