Integrated terminal not Visual Studio Code (2023)

Visual Studio Code comes with a fully integrated terminal that is conveniently launched from the root of your workspace. It offers editor integration to support features such asconnectionseerror detection.

To open the Terminal:

• Use o⌃`(Windows, LinuxCtrl+`)Keyboard shortcut to toggle the terminal panel.
• Use o⌃⇧`(Windows, LinuxCtrl+Shift+`)Keyboard shortcut for creating a new terminal.
• Use oto view>terminalorterminal>new devicemenu commands.
• Docommand paddle(⇧⌘S(Windows, LinuxCtrl+Shift+P)), Use oDisplay: Switch terminalCommand.

Observation:Open an external terminal with the⇧⌘C(Windows, LinuxCtrl+Shift+C)Keyboard shortcuts if you prefer to work outside of VS Code.

terminal shells

The built-in terminal can use various shells installed on your computer, drawing default settings from your system defaults. Shells are recognized and displayed in the terminal profile drop-down list.

For more information on configuring terminal shells, see theTerminalprofileArticle.

Manage End Devices

The terminal tabs UI is located on the right side of the terminal view. Each terminal has an entry with the group's name, icon, color and decoration (if any).

Endpoint instances can be added by selecting+icon in the upper right corner of theTERMINALControl Panel, selecting a profile from the Terminal drop-down list, or launching the⌃⇧`(Windows, LinuxCtrl+Shift+`)Command. This action creates another entry in the list of tabs associated with this endpoint.

Remove terminal instances by hovering over a tab and selecting itTrash canbutton, select a tab item and pressextinguish, useTerminal: Exit the running terminal instancecommand or via the right-click context menu.

Navigate between endpoint groups by continuing to use focus⇧⌘](Windows, LinuxCtrl+Page Down)and previous focus⇧⌘[(Windows, LinuxCtrl+Page Up).

When an endpoint's status changes, icons may appear to the right of the endpoint's title in the tab's label. Some examples are a bell (macOS) and for tasks that show a checkmark if there are no errors and an X. Mouse over the icon to read status information, which may include actions.

Groups (split windows)

Several terminals can be placed next to each other, they are called a group and are created by splitting a terminal:

• On hover, select the split line button.
• Right-click the context menu and select thedivisionsMenu option.
• Altand click on a tab that+button or the individual tab on the connector panel.
• activating the⌘\(Windows, LinuxCtrl+Shift+5)Command.

Principal:The working directory for the new terminal depends on theterminal.integrated.splitCwd Attitude.

Navigate between terminals in a group by focusing on the previous window,⌥⌘←(Windows, LinuxAlt+Links), or the next window,⌥⌘→(Windows, LinuxAlt+Right).

Dragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area lets you move a terminal from one group to another.

Moving a terminal to its own group can be done withTerminal: undivided terminalCommand via the command palette or the right-click context menu.

Staples in the editor area

Terminal in the editor area, also known as terminal editors, can be created through theTerminal: Create a new terminal in the editor areaeTerminal: Create a new terminal in the side editor panelcommands or by dragging a terminal from the terminal view into the editor area.

Terminal editors are ideal when you want a complex workbench layout, for example B. Terminals on either side of an editor, or terminals arranged in two dimensions. Below are PowerShell and WSL endpoints stacked in an editor group to the right of a file editor group.

Dieterminal.integrated.defaultLocationThe configuration can change the default location of the terminal to be in theOpinionoreditorareas.

browse the buffer

The content in the terminal is called the buffer, with the section just above the bottom viewport called "scrollback". The amount of roll retained is determined byterminal.integrated.scrollback Attitudeand enabled by default1000lines.

Several commands are available to browse the terminal buffer:

• Scroll up one line -⌥⌘image above(WindowCtrl+Alt+Page Up, LinuxCtrl+Shift+Cima)
• Scroll down one line -⌥⌘Page Down(WindowCtrl+Alt+Page Down, LinuxCtrl+Shift+Down)
• Scroll up one page -upload page(Windows, LinuxShift + Page Up)
• Scroll down one page -image down(Windows, LinuxShift+Page Down)
• Scroll up -⌘Zuhause(WindowCtrl+Home, LinuxShift+Home)
• Roll down -⌘Ende(WindowCtrl+Fim, LinuxShift+Fim)

commandNavigation is also available (seeShell-Integration):

• Scroll to previous command -⌘↑(Windows, LinuxCtrl+Up)
• Scroll to next command -⌘↓(Windows, LinuxCtrl+Down)

Scrolling is instantaneous, but can be set to animate for a short timeterminal.integrated.smoothscrollingAttitude.

connections

The endpoint has sophisticated link detection with editor integration and even link handlers contributed by extensions. Links are activated by hovering over the link so that an underline appears, then holding downctrl/beforeand click.

There are several built-in link handlers that are used in the following order of precedence:

• URIs/URLs: These are links that look like URIs, likehttps://code.visualstudio.com. They open the system browser at this point.

  (Video) Visual Studio Code Terminals Configuration

  

• File links: These are links that we verify represent files on the system. They open the file in a new editor tab and support common row/column formats such asFile:1:2,File: line 1, column 2.

  

• Folder links: These are similar to file links, but open a new VS Code window on the folder.

  

• Word Links: This is the fallback link type and uses theterminal.integrated.wordSeparatorsSetting to set word limits and convert almost all text to words. Enabling a word link will search the workspace for the word; if there is a single result, it will be opened; otherwise, search results will be displayed. Word links are considered "low confidence" and will not show an underline or tooltip unlessctrl/beforeis held. They also have limited support for row and column suffixes.

  

Extensions that handle links

Extensions can helplink providerthat allow the extension to define what happens when clicked. An example of this is theGitLensGenericNameextension recognizes git branch links.

keyboard accessibility

Links can be accessed through various keyboard commands that open links based on the type of link. These commands do not have default keyboard shortcuts.

• Terminal: Open last local file link- Opens the latest local file link.
• Terminal: Open last URL link- Opens the latest URI/URL link.
• Terminal: Open link found...- Opens a searchable quick selector with all links (including word links).

copy paste

Keyboard shortcuts for copying and pasting follow platform standards:

• Linux:Ctrl+Shift+CeCtrl+Shift+V; Collage selection is available withShift+Insert
• MacOS:Cmd+CeCommand+V
• Window:Strg+CeCtrl+V

Copying occurs automatically when you select whetherterminal.integrated.copyOnSelectionactivated.

By default when inserting multiple lines there is a warning which can be disabled withterminal.integrated.enableMultiLinePasteWarningAttitude. This only happens if the shell doesn't support "parenthesis insertion mode". When this mode is on, the shell indicates that it can handle entering multiple lines.

with the mouse

Right click behavior

Right click behavior differs by platform:

• Linux: Show context menu.
• macOS: Select the word under the cursor and display the context menu.
• Windows: Copy and drop selection if there is a selection, paste otherwise.

This can be configured withterminal.integrated.rightClickBehaviorAttitude. The options are:

• Originally- Show context menu.
• copy paste- Copy if there is a selection, paste otherwise.
• Insert- Paste on right click.
• selectWort- Select the word under the cursor and display the context menu.
• nothing- Do nothing and pass the event to the terminal.

Reposition the cursor with Alt

Altand left-clicking positions the cursor under the mouse. This works by simulating arrow keys, which may not work reliably in some shells or programs. This function can be deactivated withterminal.integrated.altClickMovesCursorAttitude.

mouse event mode

When applications running in the terminal activate mouse event mode, eg For example Vim mouse mode sends the mouse interaction to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by pressingAltkey on Windows and Linux, this can also be done with thepossibilitykey on macOS, but requires activation ofterminal.integrated.macOptionClickForcesSelectionsetup first.

To think

The integrated terminal has a search function that can be triggered with⌘F(Windows, LinuxCtrl+F).

Principal: Ctrl+Fcan be sent to the shell by removing theworkbench.action.terminal.focusFindcommand ofshell skip commands.

Run selected text

to use therunSelectedTextcommand, select the text in an editor and run the commandTerminal: Runs the selected text in the active terminalregarding thecommand paddle(⇧⌘S(Windows, LinuxCtrl+Shift+P)), the terminal tries to execute the selected text. If no text is selected in the active editor, the entire line the cursor is on is executed in the terminal.

Principal:Also run the active file with the commandworkbench.action.terminal.runActiveFile.

Maximize the terminal

The terminal display can be maximized by clicking the "Maximize panel size" button with the chevron icon pointing upwards. This temporarily hides the editors and maximizes the panel. This is useful for temporarily focusing on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel and hiding the sidebar.

choose all

There is oneTerminal: select allcommand that is boundCommand+Aon macOS, but lacks a standard key mapping on Windows and Linux because it can conflict with shell shortcut keys. UseStrg+ATo select all, add this custom keyboard shortcut:

{ "Key":"Strg+a", "Command":"workbench.action.terminal.selectAll", "When":"terminalFocus && !isMac"},

Drag and drop file paths

When you drag a file into the terminal, the path is typed into the terminal, using escape characters to match the active shell.

Automate endpoints with tasks

DietasksThe function can be used to automate launching the terminal, for example the following.vscode/tasks.jsonThe file launches a command prompt and a PowerShell terminal in a single terminal group when the window is launched:

{ "Execution":"2.0.0", "Presentation": { "Eco":INCORRECT, "discover":"always", "Focus":INCORRECT, "Panel":"dedicated", "showReuseMessage":Is correct}, "Tasks": [{ "Label":"Create terminals", "depends on": [ "First", "Second"], // Mark as default build task so cmd/ctrl+shift+b will build it "Group": { "liquid":"build", "istStandard":Is correct}, // Try to start the task when opening the folder "execute options": { "run":"Open Folder"}},{ // The name that will be displayed in the terminal tab "Label":"First", // The task starts a shell "Art":"manga", "Command":"", // Set the shell type "options": { "manga": { "executable":"cmd.exe", "Arguments": []}}, // Mark as background task to avoid spinning animation in terminal tab "isbackground":Is correct, "problem correspondent": [], // Create tasks in a group of terminals "Presentation": { "Group":"my group"}},{ "Label":"Second", "Art":"manga", "Command":"", "options": { "manga": { "executable":"pwsh.exe", "Arguments": []}}, "isbackground":Is correct, "problem correspondent": [], "Presentation": { "Group":"my group"}}]}

This file can be uploaded to the repository to be shared with other developers or created as a user task through theworkbench.action.tasks.openUserTasksCommand.

working directory

By default, the terminal opens in the folder that is open in Explorer. Theterminal.embedded.cwdThe configuration allows specifying a custom path to open:

{ "terminal.integrated.cwd":"/homewender"}

Split terminals on Windows start in the directory where the parent terminal was started. On macOS and Linux, shared terminals inherit the parent terminal's current working directory. This behavior can be changed withterminal.integrated.splitCwdAttitude:

{ "terminal.integrated.splitCwd":"WorkspaceRoot"}

Extensions are also available that offer more options, such asterminal here.

Fixed dimension clamps

DieTerminal: set fixed dimensionsThe command allows changing the number of columns and rows using the terminal and its supporting pseudo-terminal. This adds scrollbars when needed, which can make for clunky UX and is generally not recommended, but is a common question on Windows, especially for reading logs or long queues when paging tools are not available.

You can also right-click on a terminal tab and selectToggle size to content width(⌥Z(Windows, LinuxAlt+Z)) to change the number of terminal columns to the largest broken line in the terminal.

Next steps

Terminal fundamentals are covered in this document. Read on to learn more about:

• tasks- Tasks allow integration with external tools and intense use of the terminal.
• Mastering the VS Code Terminal- An external blog with many tips for advanced terminal users.
• Explore terminal commands by navigating keyboard shortcuts in VS Code (Settings: opens keyboard shortcutsthen search for 'terminal').

common questions

I'm having trouble starting the terminal

There is onededicated troubleshooting guidefor such problems.

Why is nvm complaining about a prefix option when launching the integrated terminal?

nvm (Node Version Manager) users often first see this error in VS Code's built-in terminal:

nvm is not compatible with npm configuration"Prefix"Option: currentlyTo adjustfor"/usr/local"to run`npm config delete prefix`or`nvm use --delete-prefix v8.9.1 --silent`fordisarmes

This is primarily a macOS issue and does not occur on external terminals. Typical reasons for this are as follows:

• npmwas installed globally with another instance ofitthat is somewhere in your path (like/usr/local/bin/npm).
• To use the development tools in$PATH, VS Code launches a bash login shell on startup. That means your~/.bash_profilewas already running, and when an integrated terminal is started it will runOtherLogin shell, rearranging the$PATHpossibly in unexpected ways.

To fix this problem, you need to find out where the oldnpmis installed and remove it and its deprecated node_modules. Find itnvmInitialization and execution scriptwhich npmbefore running, which should print the path when you start a new terminal.

Once you have the path to npm, find the old node_modules by resolving the symbolic link by running a command like this:

ls -la /usr/local/bin | grep"np[mx]"

This will give you the resolved path at the end:

... npm -> ../lib/node_modules/npm/bin/npm-cli.js... npx -> ../lib/node_modules/npm/bin/npx-cli.js

From there, removing the files and restarting VS Code should resolve the issue:

rm /usr/local/bin/npm /usr/local/lib/node_modules/npm/bin/npm-cli.jsrm /usr/local/bin/npx /usr/local/lib/node_modules/npm/bin/npx-cli.js

Why does macOS make a noise when I resize split terminal panes?

Keyboard shortcuts ⌃⌘← and ⌃⌘→ are the default settings for resizing individual split windows in the terminal. While they work, they also cause an "Invalid Key" system sound to play due to a Chromium issue. Therecommended workaroundis to tell macOS not to perform any operations for these key combinations by running this in your terminal:

mkdir -p ~/Biblioteca/KeyBindingscat > ~/Library/KeyBindings/DefaultKeyBinding.dict<<EOF{"^@\UF701" = "noop";"^@\UF702" = "noop";"^@\UF703" = "noop";}EOF

I'm having problems with terminal rendering. What can I do?

By default, the integrated terminal renders with GPU acceleration on most computers. When there are rendering issues, it's usually because something in your hardware/OS/drivers isn't working well with the GPU renderer. The first thing to try is disabling GPU acceleration and switching rendering speed to more reliable DOM-based rendering:

{ "terminal.integrated.gpuAcceleration":"the end"}

see theGPU accelerationsection for more information.

I understand1~or[201~when i paste something

This usually means that the program/shell running in the terminal has asked to enable "bracket insertion mode", but something doesn't support it properly. To get around this, you can runprintf "\e[?2004l"to disable it for this session or add the following to your~/.inputrcArchive:

suspend activate-bracket-paste

Ctrl+A, Ctrl+R imprime ^A, ^R em zsh

This can happen due to configuration when zsh is in vim mode instead of emacs mode$EDITORor$VISIBLEforvi/vimin your startup scripts.

To get around this, you have two options:

• Make sure you don't commit$EDITORforvi(m). However, this is not an option if you want your git editor to work.
• Add tobinding key -eto your startup script to explicitly configure Emacs.

How can I configure cmd+. to Ctrl+C as macOS built-in terminal?

macOS default terminal is usedcommand+.do the same asStrg+C. To get this behavior in VS Code add the followingcustom key mapping:

{ "Key":"cmd+.", "Command":"workbench.action.terminal.sendSequence", "When":"Terminal Focus", "Arguments": {"Text":"\u0003"}}

Why are the colors in the terminal wrong?

One of our accessibility features, which we turn on by default, is ensuring that foreground text maintains a minimum contrast ratio of at least 4.5. This feature ensures that the text is readable regardless of the shell and theme used, which is otherwise not possible. To disable this feature, you can set the following:

"terminal.integrated.minimumContrastRatio":1

see theMinimal Contrast Systemsection for more information.

12/07/2022