Flatpak-warning running an unofficial Flatpak version of Visual Studio Code
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 25/100
Research direction
The report names no repository files, tests, or concrete change. Start by reproducing the warning from the Flatpak installation described, then clarify the intended behavior and identify the relevant project entry point; done would require an agreed change and a regression check.
Written by the indexing model from the issue text.
Description
am getting this txt file warning on opening the flatpak from ubuntu app store after installing it through flatpak cli
| Warning: You are running an unofficial Flatpak version of Visual Studio Code !!! |
Please open issues under: https://github.com/flathub/com.visualstudio.code/issues
This version is running inside a container and is therefore not able
to access SDKs on your host system!
To execute commands on the host system, run inside the sandbox:
$ host-spawn
To make the Integrated Terminal automatically use the host system's shell,
you can add this to the settings:
{
"terminal.integrated.defaultProfile.linux": "bash",
"terminal.integrated.profiles.linux": {
"bash": {
"path": "host-spawn",
"args": ["bash"]
}
}
}
This Flatpak provides a standard development environment (gcc, python, etc).
To see what's available:
$ flatpak run --command=sh com.visualstudio.code
$ ls /usr/bin (shared runtime)
$ ls /app/bin (bundled with this flatpak)
To get support for additional languages or tools within the Flatpak, 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
Similarly for shells and other tools:
$ flatpak install com.visualstudio.code.tool.fish
$ flatpak install com.visualstudio.code.tool.podman
You can use
$ flatpak search
to find others.
- Dominant language
- Shell
- Stars
- 217
- Forks
- 81
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flathub/com.visualstudio.code
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
flathub/com.visualstudio.code#679 · 4 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
flathub/com.visualstudio.code#563 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flathub/com.visualstudio.code#388 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
flathub/com.visualstudio.code#715 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
flathub/com.visualstudio.code#710 ·
All issues in flathub/com.visualstudio.code
Similar issues
-
area:release bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
registrystack/registry-stack#1874 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppImage/appimage.github.io#9676 ·
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
a2aproject/A2A#2289 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
YunoHost-Apps/pixelfed_ynh#346 ·