Visual Studio Terminal

 admin

  1. Visual Studio Terminal
  2. Show Console In Visual Studio Terminal
  • Go to the settings (In VSCode obviously) On Windows/Linux - File Preferences Settings. On macOS - Code Preferences Settings. Shortcut (⌘,) Search (⇧⌘P) → “Preferences: Open Settings”. Search for 'workbench: color customizations' and open the settings.json file. Edit or Paste your configuration under workbench.
  • I'm using Visual Studio Code for my various web projects. VS Code recently releases version 1.2. One of the key feature in this release is in-built Terminal, which is docked in VS Code. In Windows machines Command Prompt, we can enable quick edit mode to paste the text from our clipboard by using right-click mouse. Windows shortcut.

Visual Studio Live Share lets you collaboratively edit and debug any codebase with others in real time—each person working in their own familiar, personalized environment.

If you are new to using the Visual Studio Code Integrated Terminal, you can learn more in the Integrated Terminal user guide. There you can read how to configure the terminal, as well as review answers to common questions.

Below are specific troubleshooting steps, if the user guide hasn't helped you diagnose the launch failure. The troubleshooting steps, such as checking your settings and enabling logging, apply to all platforms that support VS Code; macOS, Linux, and Windows.

Note: If you're on Windows, review the common issues on Windows section first.

Troubleshooting steps

To troubleshoot Integrated Terminal launch failures in Visual Studio Code, follow these steps to diagnose issues:

  1. Check your user settings. Review these terminal.integratedsettings that could affect the launch:

    • terminal.integrated.shell.{platform} - The path of the shell that the terminal uses.
    • terminal.integrated.shellArgs.{platform} - The command-line arguments when launching the shell process.
    • terminal.integrated.cwd - The current working directory (cwd) for the shell process.
    • terminal.integrated.env.{platform} - Environment variables that will be added to the shell process.
    • terminal.integrated.inheritEnv - Whether new shells should inherit their environment from VS Code.
    • terminal.integrated.automationShell.{platform} - Shell path for automation-related terminal usage like tasks and debug.
    • terminal.integrated.splitCwd - Controls the current working directory a split terminal starts with.
    • terminal.integrated.windowsEnableConpty - Whether to use ConPTY for Windows terminal process communication.

    You can review settings in the Settings editor (File > Preferences > Settings) and search for specific settings by the setting ID.

    A quick way to check if you have changed settings that you might not be aware of, is to use the @modified filter in the Settings editor.

    Most Integrated Terminal settings will need to be modified directly in your user settings.json JSON file. You can open settings.json via the Edit in settings.json link in the Settings editor or with the Preferences: Open Settings (JSON) command from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

  2. Test your shell directly. Try running your designated integrated terminal shell outside VS Code from an external terminal or command prompt. Some terminal launch failures may be due to your shell installation and are not specific to VS Code. The exit codes displayed come from the shell and you may be able to diagnose shell issues by searching on the internet for the specific shell and exit code.

  3. Use the most recent version of VS Code. Each VS Code monthly release has many updates and fixes and may include integrated terminal improvements. You can check your VS Code version via Help > About (on macOS Code > About Visual Studio Code). To find the latest version of VS Code, go to the VS Code release notes. You may also want to check that you have installed the latest version of your shell.

  4. Enable trace logging. You can enable trace logging and capture a log when launching the terminal. Logging often reveals what is wrong as all arguments used to create the terminal process/pty are recorded. Bad shell names, arguments, or environment variables can cause the terminal to not launch. Keep this log for later if your problem isn't solved.

Additional troubleshooting steps

If none of these steps helped solve the issue, you can also try:

  • Ask about it on Stack Overflow, often launch issues are related to environment setup and not a problem with VS Code.
  • If the terminal is being launched from an extension, report the issue to the extension by opening the issue reporter (Help > Report Issue) and set File On = 'An Extension'
  • If you believe it to be a bug with VS Code, report the issue using the issue reporter (Help > Report Issue). The issue reporter will autofill relevant information, see Creating great terminal issues for what else to include in the report.
  • If you're on Windows 10 1809 (build 17763) or below, the issue is related to the legacy 'winpty' backend. Upgrading to Windows 1903 (build 18362) will move you onto the new 'conpty' backend that is built by Microsoft and could fix your problem.

Exit codes

The exit codes displayed in the terminal launch failure notification are returned from the shell process and are not generated by VS Code. There are many available shells that can be used in the terminal and hundreds of possible exit codes. Try searching on the internet for your specific shell and exit code (for example, 'PowerShell 4294901760') and you may find specific suggestions or known issues related to your terminal launch failure.

Common issues on Windows

Make sure compatibility mode is disabled

When upgrading to Windows 10, some apps may have compatibility mode turned on automatically. When this happens with VS Code, the terminal breaks as it does some low level things to enable the emulation it uses. You can check and disable compatibility mode by right-clicking on the VS Code executable and selecting properties, then uncheck the Run this program in compatibility mode option in the compatibility tab.

The terminal exited with code 1 on Windows 10 (with WSL as the default shell)

This can happen if Windows Subsystem for Linux (WSL) is not set up with a valid default Linux distribution.

Note: 'docker-desktop-data' is not a valid distribution.

  • Open PowerShell and enter wslconfig.exe /l to confirm WSL is installed correctly and list the currently available Linux distributions within your system. Confirm a valid distribution has (default) next to it.
  • To change the default distribution, enter wslconfig.exe /setdefault 'distributionNameAsShownInList'

The terminal not working when running the 32-bit Windows client on 64-bit Windows?

The easy fix for this issue is to use the 64-bit version. If you must use the 32-bit version, you need to use the sysnative path when configuring your shell path instead of System32. Adding this setting should fix the issue:

A native exception occurred

Typically this error occurs due to anti-virus software intercepting and blocking the winpty/conpty components from creating the terminal process. To work around this error, you can exclude the following file from your anti-virus scanning:

Reporting this issue to the Anti-virus team can also help stamp out the issue all together.

Terminal exits with code 3221225786 (or similar)

This can happen when you have legacy console mode enabled in conhost's properties. To change this, open cmd.exe from the start menu, right-click the title bar, go to Properties and under the Options tab, uncheck Use legacy console.

Run terminal command directly in Text Editor

Notice

From v0.0.4, this extension will have limited updates for bug fix or feature development, because:

  1. I have another extension: Code Runner which is superset of the Terminal extension since it not only supports powershell, bat/cmd, bash/sh but also supports other script language like js, php, python, perl, ruby, go, lua, groovy, vbscript even F#, C#. Moreover, this Code Runner extension has more functions (e.g. working directory support, output syntax highlight, run as a file instead of running a set of commands and so on) and will have more supports and updates in the future.

  2. VS Code already has basic built-in support for the terminal from v1.2 and add 'run selected text' in v1.3. Besides, the ability to run the entire text of current active text editor will come in v1.5. I have already sent the Pull request and it has been merged.

Features

  • Run all the commands in Text Editor
  • Run the selected commands in Text Editor
  • Stop the running commands
  • View output in Output Window
  • Open Integrated Terminal at current file's directory
  • Quick way to toggle Integrated Terminal

Usages

  • Write or select a set of commands in Text Editor, then use shortcut Ctrl+Alt+R, or press F1 and then select/type Run Terminal Command, the commands will run and the output will be shown in the Output Window.
  • To stop the running commands, use shortcut Ctrl+Alt+C, or press F1 and then select/type Stop Terminal Command
  • To open Integrated Terminal at current file's directory, use shortcut Ctrl+Alt+O, or press F1 and then select/type Open in Integrated Terminal, or right click in Text Editor/Explorer and then click Open in Integrated Terminal in context menu
  • To toggle Integrated Terminal, use shortcut Ctrl+Alt+T, or click the Terminal icon in the Status Bar at the bottom

Telemetry data

By default, telemetry data collection is turned on. To disable it, update the settings.json as below:

Change Log

Visual Studio Terminal

0.0.10 (2017-07-22)

Visual Studio Terminal
  • #10: Handle case-insensitive bash path

0.0.9 (2017-07-20)

  • #9: Open terminal for Bash on Windows

0.0.8 (2017-05-15)

  • Quick way to toggle Integrated Terminal in the Status Bar

0.0.7

  • Add 'Open in Integrated Terminal' context menu

0.0.6

  • Upgrade applicationinsights npm since telemetry data requires HTTPS

0.0.5

  • Add Application Insights to track telemetry data

0.0.4

  • Update the future of this extension

0.0.3

  • Add support to stop running commands
Visual Studio Terminal

0.0.2

Visual Studio Terminal

  • Update README.md and add GitHub info

0.0.1

  • Initial Release

Issues

Submit the issues if you find any bug or have any suggestion.

Contribution

Show Console In Visual Studio Terminal

Fork the repo and submit pull requests.