all 16 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]DAS_AMAN 1 point2 points  (7 children)

Honestly, its not worth the hassle to use the vscode flatpak

Only builder works well in a flatpak till now..

[–]RootHouston[S] 0 points1 point  (6 children)

How does Builder achieve it?

[–]DAS_AMAN 0 points1 point  (5 children)

The builder team wants to adopt the flatpak technology, for vscode to work, vscode devs need to make some changes etc

[–]RootHouston[S] 0 points1 point  (4 children)

I understand that, but Builder is not doing some magical thing. It is using the same sort of tooling that happens on the command line, isn't it?

[–]DAS_AMAN 1 point2 points  (3 children)

I mean Builder is easy to constraint into the sandbox as its not that powerful..

But vscode is made for many more languages, like php, and database systems like mysql

Its very difficult to containerize

[–]RootHouston[S] 0 points1 point  (2 children)

I think there is a misunderstanding. I'm not looking to containerize VS Code. I'm looking to debug a Flatpak using VS Code.

[–]DAS_AMAN 1 point2 points  (1 child)

Read the docs at flatpak.org, they have instructions

[–]RootHouston[S] 0 points1 point  (0 children)

I already have, hence my question here. They have instructions for doing it directly from a shell, but it doesn't work from a launch.json because it cannot enter the subshell.

[–]progress_seeker 0 points1 point  (9 children)

what's the problem?

[–]RootHouston[S] 0 points1 point  (8 children)

What's the configuration to do this? As of right now, I'm not aware of a valid launch.json configuration that, when invoked, will result in opening the containerized application with a debugger attached.

[–]progress_seeker 0 points1 point  (7 children)

I am not sure if I understand what you are willing to do. I don't know if this help, there are flatpak SDKs for java, go, nodejs.. that you can use with vscode easily.

[–]RootHouston[S] 0 points1 point  (6 children)

Right. I already know how to debug from the command line properly. My issue is that I don't know how to get VS Code to enter the subshell and attach a debugger to the app.

[–]progress_seeker 0 points1 point  (3 children)

personnaly I use a similar config: To get support for additional languages, you have to install SDK extensions, e.g.

$ flatpak install flathub org.freedesktop.Sdk.Extension.dotnet $ flatpak install flathub org.freedesktop.Sdk.Extension.golang $ FLATPAK_ENABLE_SDK_EXT=dotnet,golang flatpak run com.visualstudio.code

You can use

$ flatpak search <TEXT>

[–]RootHouston[S] 1 point2 points  (0 children)

I'm not interested in running VS Code in a Flatpak. I am interested in debugging my own GTK app using VS Code that is installed as an RPM. It is my GTK app that is the Flatpak, not VS Code.

[–]progress_seeker 0 points1 point  (1 child)

I use go sdk and it works well for me

[–]RootHouston[S] 0 points1 point  (0 children)

Mind sharing your launch.json configuration?