GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - wavetermdev/dev.commandline.waveterm

BranchesTags
Open more actions menu
 
 

Latest commit

 

History

426 Commits
426 Commits

Folders and files

NameName
Last commit message
Last commit date
icons
icons
 
 
shared-modules @ 1673277
shared-modules @ 1673277
 
 
.gitignore
.gitignore
 
 
.gitmodules
.gitmodules
 
 
README.md
README.md
 
 
dev.commandline.waveterm.desktop
dev.commandline.waveterm.desktop
 
 
dev.commandline.waveterm.metainfo.xml
dev.commandline.waveterm.metainfo.xml
 
 
dev.commandline.waveterm.yaml
dev.commandline.waveterm.yaml
 
 
flathub.json
flathub.json
 
 

Repository files navigation

Visual Studio Code Flatpak

🚨 Warning: This is an unofficial Flatpak build of Visual Studio Code, generated from the official Microsoft-built .deb packages here.

Table of Contents

  • Usage
    • Execute commands in the host system.
    • Use host shell in the integrated terminal.
    • Support for language extension.
  • Support

Usage

Most functionality works out of the box, though please note that flatpak runs in an isolated environment and some work is necessary to enable those features.

Execute commands in the host system.

To execute commands on the host system, run inside the sandbox:

$ flatpak-spawn --host <COMMAND>

or

$ host-spawn <COMMAND>

  • Most users seem to report a better experience with host-spawn

Use host shell in the integrated terminal.

Another option to execute commands is to use your host shell in the integrated terminal instead of the sandbox one.

For that go to File -> Preferences -> Settings and find Features > Terminal > Integrated > Profiles, then click on Edit in settings.json (The important thing here is to open settings.json)

And make sure that you have the following lines there:

flatpak-spawn --host

{
  "terminal.integrated.defaultProfile.linux": "bash",
  "terminal.integrated.profiles.linux": {
    "bash": {
      "path": "/usr/bin/flatpak-spawn",
      "args": ["--host", "--env=TERM=xterm-256color", "bash"],
      "icon": "terminal-bash",
      "overrideName": true
    }
  }
}

host-spawn

{
  "terminal.integrated.defaultProfile.linux": "bash",
  "terminal.integrated.profiles.linux": {
    "bash": {
      "path": "/app/bin/host-spawn",
      "args": ["bash"],
      "icon": "terminal-bash",
      "overrideName": true
    }
  }
}
  • You can change bash to any terminal you are using: zsh, fish, sh.
  • overrideName allows for the 'name' (or whatever you set it to) of the shell you're using to appear (e.g. normally zsh, fish, sh).

Support for language extension.

Some Visual Studio extension depends on packages that might exist on your host, but they are not accessible thought Flatpak. Like support to programming languages: gcc, python, etc..

See available SDK:

$ flatpak run --command=sh com.visualstudio.code
$ ls /usr/bin (shared runtime)
$ ls /app/bin (bundled with this flatpak)

Getting 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

Finding other SDK

flatpak search <TEXT>

Support

Please open issues under: https://github.com/flathub/com.visualstudio.code/issues

About

flathub.org/apps/details/com.visualstudio.code

Resources

Readme
Activity
Custom properties

Stars

3 stars

Watchers

0 watching

Forks

1 fork
Report repository

Releases

Packages

Used by

Contributors

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.