search

flathub / org.kde.kate

https://flathub.org/apps/details/org.kde.kate
3 stars 5 forks source link

Need access to --filesystem=/usr/include #27

Open Waqar144 opened 1 year ago

Waqar144 commented 1 year ago

When writing code, one often needs to access the header files in that directory. This is super important as if one can't jump to the location of header files the editor will not be usable.

Seems like just adding --filesystem=/usr/include will not work. Is this even supported?

/usr/include is just one example. There can be many such directories in the system that need to be accessible.

travier commented 1 year ago

We can not expect includes to be installed in the host. Those should be in a container, using toolbox or distrobox. Does Kate has a remote container plugin like VS Code?

Waqar144 commented 1 year ago

Not sure I understand you. Kate doesn't have a container plugin of any kind right now. And even if it did, how would it help?

Many users don't use containers for development. Missing access to /usr/ breaks workflow for myself in a pretty significant way.

travier commented 1 year ago

We could use host-os from https://man.archlinux.org/man/flatpak-metadata.5.en but it will need special handling anyway.

Waqar144 commented 1 year ago

I think there is no way to solve this cleanly atm. Once you have access to /usr/, the difference between a sandbox / host-app is nil. Maybe we'll have a clean way to do this in future or maybe there already is. Will check what gnome-builder does as it also supports LSP and C/C++.

Regardless, the current state of flatpak-Kate is useful as-is for many users. A lot of new languages don't install their stuff in /usr, unless you really want. E.g., Go, dart, javascript and even rust can be in your home directory and will be accessible.

travier commented 1 year ago

GNOME Builder has support for running things in containers via podman or toolbox.

KhazAkar commented 1 year ago

Yes, but this is sort-of remote development support, which Kate does not currently have in any way, shape or form. Additionally, GNOME Builder seems much more as IDE than Kate, which is more like VSCode competitor, not Visual Studio (non VSCode one) one.

christoph-cullmann commented 9 months ago

I think the point is that Kate allows to use the tools from outside the container but we end up opening files inside of it if these output paths into /usr/.... For our use case having access to /usr/include of the host would be the right solution.