Vs code freepascal linux

Visual Studio Code on Linux

Installation

See the Download Visual Studio Code page for a complete list of available installation options.

By downloading and using Visual Studio Code, you agree to the license terms and privacy statement.

Debian and Ubuntu based distributions

The easiest way to install Visual Studio Code for Debian/Ubuntu based distributions is to download and install the .deb package (64-bit), either through the graphical software center if it’s available, or through the command line with:

Note that other binaries are also available on the VS Code download page.

Installing the .deb package will automatically install the apt repository and signing key to enable auto-updating using the system’s package manager. Alternatively, the repository and key can also be installed manually with the following script:

Then update the package cache and install the package using:

RHEL, Fedora, and CentOS based distributions

We currently ship the stable 64-bit VS Code in a yum repository, the following script will install the key and repository:

Then update the package cache and install the package using dnf (Fedora 22 and above):

Or on older versions using yum :

Due to the manual signing process and the system we use to publish, the yum repo may lag behind and not get the latest version of VS Code immediately.

Visual Studio Code is officially distributed as a Snap package in the Snap Store:

You can install it by running:

Once installed, the Snap daemon will take care of automatically updating VS Code in the background. You will get an in-product update notification whenever a new update is available.

Note: If snap isn’t available in your Linux distribution, please check the following Installing snapd guide, which can help you get that set up.

Learn more about snaps from the official Snap Documentation.

openSUSE and SLE-based distributions

The yum repository above also works for openSUSE and SLE-based systems, the following script will install the key and repository:

Then update the package cache and install the package using:

AUR package for Arch Linux

To get more information about the installation from the AUR, please consult the following wiki entry: Install AUR Packages.

Nix package for NixOS (or any Linux distribution using Nix package manager)

There is a community maintained VS Code Nix package in the nixpkgs repository. In order to install it using Nix, set allowUnfree option to true in your config.nix and execute:

Installing .rpm package manually

The VS Code .rpm package (64-bit) can also be manually downloaded and installed, however, auto-updating won’t work unless the repository above is installed. Once downloaded it can be installed using your package manager, for example with dnf :

Note that other binaries are also available on the VS Code download page.

Updates

VS Code ships monthly and you can see when a new release is available by checking the release notes. If the VS Code repository was installed correctly, then your system package manager should handle auto-updating in the same way as other packages on the system.

Note: Updates are automatic and run in the background for the Snap package.

Node.js

Node.js is a popular platform and runtime for easily building and running JavaScript applications. It also includes npm, a Package Manager for Node.js modules. You’ll see Node.js and npm mentioned frequently in our documentation and some optional VS Code tooling requires Node.js (for example, the VS Code extension generator).

If you’d like to install Node.js on Linux, see Installing Node.js via package manager to find the Node.js package and installation instructions tailored to your Linux distribution. You can also install and support multiple versions of Node.js by using the Node Version Manager.

To learn more about JavaScript and Node.js, see our Node.js tutorial, where you’ll learn about running and debugging Node.js applications with VS Code.

Setting VS Code as the default text editor

xdg-open

You can set the default text editor for text files ( text/plain ) that is used by xdg-open with the following command:

Debian alternatives system

Debian-based distributions allow setting a default editor using the Debian alternatives system, without concern for the MIME type. You can set this by running the following and selecting code:

If Visual Studio Code doesn’t show up as an alternative to editor , you need to register it:

Windows as a Linux developer machine

Another option for Linux development with VS Code is to use a Windows machine with the Windows Subsystem for Linux (WSL).

Windows Subsystem for Linux

With WSL, you can install and run Linux distributions on Windows. This enables you to develop and test your source code on Linux while still working locally on a Windows machine. WSL supports Linux distributions such as Ubuntu, Debian, SUSE, and Alpine available from the Microsoft Store.

When coupled with the Remote — WSL extension, you get full VS Code editing and debugging support while running in the context of a Linux distro on WSL.

See the Developing in WSL documentation to learn more or try the Working in WSL introductory tutorial.

Next steps

Once you have installed VS Code, these topics will help you learn more about it:

• Additional Components — Learn how to install Git, Node.js, TypeScript, and tools like Yeoman.
• User Interface — A quick orientation to VS Code.
• User/Workspace Settings — Learn how to configure VS Code to your preferences through settings.

Common questions

Azure VM Issues

I’m getting a «Running without the SUID sandbox» error?

You can safely ignore this error.

Debian and moving files to trash

If you see an error when deleting files from the VS Code Explorer on the Debian operating system, it might be because the trash implementation that VS Code is using is not there.

Run these commands to solve this issue:

Conflicts with VS Code packages from other repositories

Some distributions, for example Pop!_OS provide their own code package. To ensure the official VS Code repository is used, create a file named /etc/apt/preferences.d/code with the following content:

«Visual Studio Code is unable to watch for file changes in this large workspace» (error ENOSPC)

When you see this notification, it indicates that the VS Code file watcher is running out of handles because the workspace is large and contains many files. Before adjusting platform limits, make sure that potentially large folders, such as Python .venv , are added to the files.watcherExclude setting (more details below). The current limit can be viewed by running:

The limit can be increased to its maximum by editing /etc/sysctl.conf (except on Arch Linux, read below) and adding this line to the end of the file:

The new value can then be loaded in by running sudo sysctl -p .

While 524,288 is the maximum number of files that can be watched, if you’re in an environment that is particularly memory constrained, you may want to lower the number. Each file watch takes up 1080 bytes, so assuming that all 524,288 watches are consumed, that results in an upper bound of around 540 MiB.

Arch-based distros (including Manjaro) require you to change a different file; follow these steps instead.

Another option is to exclude specific workspace directories from the VS Code file watcher with the files.watcherExclude setting. The default for files.watcherExclude excludes node_modules and some folders under .git , but you can add other directories that you don’t want VS Code to track.

I can’t see Chinese characters in Ubuntu

We’re working on a fix. In the meantime, open the application menu, then choose File > Preferences > Settings. In the Text Editor > Font section, set «Font Family» to Droid Sans Mono, Droid Sans Fallback . If you’d rather edit the settings.json file directly, set editor.fontFamily as shown:

Package git is not installed

This error can appear during installation and is typically caused by the package manager’s lists being out of date. Try updating them and installing again:

The code bin command does not bring the window to the foreground on Ubuntu

Running code . on Ubuntu when VS Code is already open in the current directory will not bring VS Code into the foreground. This is a feature of the OS which can be disabled using ccsm .

Under General > General Options > Focus & Raise Behaviour, set «Focus Prevention Level» to «Off». Remember this is an OS-level setting that will apply to all applications, not just VS Code.

Cannot install .deb package due to «/etc/apt/sources.list.d/vscode.list: No such file or directory»

This can happen when sources.list.d doesn’t exist or you don’t have access to create the file. To fix this, try manually creating the folder and an empty vscode.list file:

Cannot move or resize the window while X forwarding a remote window

If you are using X forwarding to use VS Code remotely, you will need to use the native title bar to ensure you can properly manipulate the window. You can switch to using it by setting window.titleBarStyle to native .

Using the custom title bar

The custom title bar and menus were enabled by default on Linux for several months. The custom title bar has been a success on Windows, but the customer response on Linux suggests otherwise. Based on feedback, we have decided to make this setting opt-in on Linux and leave the native title bar as the default.

The custom title bar provides many benefits including great theming support and better accessibility through keyboard navigation and screen readers. Unfortunately, these benefits do not translate as well to the Linux platform. Linux has a variety of desktop environments and window managers that can make the VS Code theming look foreign to users. For users needing the accessibility improvements, we recommend enabling the custom title bar when running in accessibility mode using a screen reader. You can still manually set the title bar with the Window: Title Bar Style ( window.titleBarStyle ) setting.

Broken cursor in editor with display scaling enabled

Due to an upstream issue #14787 with Electron, the mouse cursor may render incorrectly with scaling enabled. If you notice that the usual text cursor is not being rendered inside the editor as you would expect, try falling back to the native menu bar by configuring the setting window.titleBarStyle to native .

Repository changed its origin value

If you receive an error similar to the following:

Use apt instead of apt-get and you will be prompted to accept the origin change:

Источник

Remote Development with Linux

Linux is a highly variable environment and the large number of server, container, and desktop distributions can make it difficult to know what is supported. Visual Studio Code Remote Development has prerequisites for the specific host / container / WSL distribution you will be connecting to.

The extensions are known to work when connecting to recent stable/LTS version of:

• Ubuntu 64-bit x86, ARMv8l (AArch64) (16.04+, IoT 18.04+)
• Debian 64-bit x86, ARMv8l (AArch64) (Stretch/9+)
• Raspbian ARMv7l (AArch32) 32-bit (Stretch/9+)
• CentOS / RHEL 64-bit x86 (7+)
• Alpine Linux 64-bit x86 containers or WSL hosts (3.9+) in Remote — Containers, Remote — WSL

The following non-Linux SSH hosts are also supported:

• Windows 10 / Server 2016/2019 SSH hosts (1803+) using the official OpenSSH Server and enabling remote.SSH.useLocalServer in VS Code settings.
• macOS 10.14+ (Mojave) SSH hosts with Remote Login enabled.

However, if you are using a non-standard configuration or downstream distribution of Linux, you may run into issues. This document provides information on requirements as well as tips to help you get up and running even if your configuration is only community-supported.

Note that other extensions may have dependencies beyond those listed here. Some extensions also contain compiled native code that may not work on Alpine Linux, or ARMv7 (AArch32), or ARMv8 (AArch64). These platforms are considered in «preview» for this reason. If you encounter an issue that only occurs with a particular extension, contact the extension authors for information on their native dependencies.

Local Linux prerequisites

If you are running Linux locally, the VS Code prerequisites drive most of the requirements.

In addition, specific Remote Development extensions have further requirements:

• Remote — SSH: ssh needs to be in the path. The shell binary is typically in the openssh-client package.
• Remote — Containers: Docker CE/EE 18.06+ and Docker Compose 1.21+. Follow the official install instructions for Docker CE/EE for your distribution. If you are using Docker Compose, follow the Install Docker Compose directions as well. (Note that the Ubuntu Snap package is not supported and packages in distributions may be out of date.) docker and docker-compose must also be in the path. However, Docker does not need to be running if you are using a remote host.

Remote host / container / WSL Linux prerequisites

Platform prerequisites are primarily driven by the version of the Node.js runtime (and by extension the V8 JavaScript engine) shipped in the server component automatically installed on each remote endpoint. This server also has a set of related native node modules that need to be compiled and tested for each target. 64-bit x86 glibc-based Linux distributions currently provide the best support given these requirements.

You may encounter issues with certain extensions with native dependencies with ARMv7l (AArch32) / ARMv8l (AArch64) glibc-based hosts, containers, or WSL and 64-bit x86 musl-based Alpine Linux. For ARMv7l/ARMv8l, extensions may only include x86_64 versions of native modules or runtimes in the extension. For Alpine Linux, included native code or runtimes may not work due to fundamental differences between how libc is implemented in Alpine Linux ( musl ) and other distributions ( glibc ). In both these cases, extensions will need to opt-in to supporting these platforms by compiling / including binaries for these additional targets. Please raise an issue with the appropriate extension author requesting support if you encounter an extension that does not work as expected.

Distribution	Base Requirements	Remote — SSH Requirements	Notes
General	kernel >= 3.10, glibc >=2.17, libstdc++ >= 3.4.18, Python 2.6 or 2.7, tar	OpenSSH server, bash , and curl or wget	Run ldd —version to check the glibc version. Run strings /usr/lib64/libstdc++.so.6 | grep GLIBCXX to see if libstdc++ 3.4.18 is available.
Ubuntu 16.04+, Debian 8+, Raspbian Stretch/9+ and downstream distributions	libc6 libstdc++6 python-minimal ca-certificates tar	openssh-server bash and curl or wget	Requires kernel >= 3.10, glibc >= 2.17, libstdc++ >= 3.4.18. Debian glibc libgcc libstdc++ python ca-certificates tar	openssh-server bash and curl or wget	Requires kernel >= 3.10, glibc >= 2.17, libstdc++ >= 3.4.18. RHEL / CentOS musl libgcc libstdc++ . musl >= 1.1.18, glibc not required.	Not yet supported.	Supported in Remote — Containers and Remote — WSL. Extensions installed in the container may not work due to glibc dependencies in extension native code.
openSUSE Leap / SUSE Linux Enterprise 15+	glibc libgcc_s1 libstdc++6 python ca-certificates gzip tar	curl or wget	Requires kernel >= 3.10, glibc, libstdc++6

Tips by Linux distribution

The following is a list of distributions and any base requirements that may be missing. End-of-life versions of distributions are not included.

• ✅ = Working
• ⚠️ = Working, but see note for limitations
• 🔬 = Experimental
• 🛑 = Unsupported, but has workaround
• ❌ = Unsupported

Server Distribution	Docker Image	Missing libraries	Notes / additional steps
⚠️ Alpine Linux 3.10 (64-bit)	alpine:3.10	libgcc libstdc++	Supported in Remote — Containers and Remote — WSL only. Some extensions installed in the container may not work due to glibc dependencies in extension native code.
✅ CentOS 7 Server (64-bit)	centos:7
🛑 CentOS 6 Server (64-bit)	centos:6	glibc >= 2.17, libstdc++ >= 3.4.18	Requires a workaround.
✅ Debian 10 Server (64-bit)	debian:10
✅ Debian 9 Server (64-bit)	debian:9
✅ openSUSE Leap Server 15 (64-bit)	opensuse/leap:15	Docker image is missing tar and gzip .
✅ openSUSE Leap Server 42.3 (64-bit)	opensuse/leap:42.3	Docker image is missing tar and gzip .
✅ Oracle Linux 7 (64-bit)	oraclelinux:7
🛑️ Oracle Linux 6 (64-bit)	oraclelinux:6	glibc >= 2.17, libstdc++ >= 3.4.18. Docker image is missing tar .	Requires a workaround.
⚠️ Raspbian Stretch/9 (ARMv7l 32-bit)	Some extensions may not work when installed on an ARMv7l host due to extension x86 native code. Remote — Containers does support connecting to containers on an ARM host.
✅ RedHat Enterprise Linux 7 (64-bit)
🛑 RedHat Enterprise Linux 6 (64-bit)	glibc >= 2.17, libstdc++ >= 3.4.18	Requires a workaround.
✅ SUSE Linux Enterprise Server 15 (64-bit)	Docker image is missing tar and gzip .
✅ SUSE Linux Enterprise Server 12 (64-bit)	Docker image is missing tar and gzip .
❌ SUSE Linux Enterprise Server 11 (64-bit)	glibc >= 2.17, libstdc++ >= 3.4.18	Might work compiling glibc from source, but untested.
⚠️ Ubuntu 18.04 IoT (ARMv8l 64-bit)	Some extensions may not work when installed on an ARMv8l host due to extension x86 native code. Remote — Containers does support connecting to containers on an ARM host.
✅ Ubuntu Server 20.04 (64-bit)	ubuntu:20.04
✅ Ubuntu Server 19.04 (64-bit)	ubuntu:19.04
✅ Ubuntu Server 18.04 (64-bit)	ubuntu:18.04
✅ Ubuntu Server 16.04 (64-bit)	ubuntu:16.04
✅ Ubuntu Server 14.04 (64-bit)	ubuntu:14.04

Updating glibc and libstdc++ on RHEL / CentOS 6

RHEL / CentOS 6 ships with glibc 2.12 and libstdc++ 3.4.13. Unfortunately, this does not meet the requirements for Remote Development. RHEL / CentOS 6 goes out of support in 2020, so we strongly recommend upgrading to RHEL / CentOS 7 or higher.

However, as a workaround, you can either build glibc manually or use the following script to install updated binaries. The bash script below will upgrade these libraries without having to build them. It is adapted from information in this article, this gist, and this Fedora copr project. The article also includes instructions for manually building glibc if you would prefer not to use the binaries from the article.

Do not run this script on anything mission critical without a rollback strategy since it does update libraries that other applications depend on.

For servers, run the following script and restart the server so the updates take effect.

In a container environment, you can add similar contents to a Dockerfile:

Источник