You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/terminal/appearance.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ Terminal tabs appear on the right of the terminal view when there are two or mor
60
60
61
61
The default visibility is designed to save horizontal space, but may not be desirable. How tabs are presented can be configured with the following settings:
62
62
63
-
-`setting(terminal.integrated.tabs.hideCondition)`: When to hide the tabs to the right, set to `"never"` to always show them.
63
+
-`setting(terminal.integrated.tabs.hideCondition)`: When to hide the tabs to the right, set to `never` to always show them.
64
64
-`setting(terminal.integrated.tabs.showActiveTerminal)`: When to show the active terminal in the terminal view header.
65
65
-`setting(terminal.integrated.tabs.showActions)`: When to show the active terminal's actions in the view header.
66
66
-`setting(terminal.integrated.tabs.location)`: Whether the tabs should be shown on the left or right of the terminal.
@@ -166,7 +166,7 @@ The terminal features two different renderers, each of which have different trad
166
166
167
167
GPU acceleration driven by the WebGL renderer is enabled in the terminal by default. This helps the terminal work faster and display at a high FPS by significantly reducing the time the CPU spends rendering each frame.
168
168
169
-
The default `setting(terminal.integrated.gpuAcceleration)` value of `"auto"` tries the WebGL renderer and if it failed will fall back to the DOM renderer. When on Linux VMs, browsers that don't support WebGL, or machines with outdated drivers, WebGL may not work properly.
169
+
The default `setting(terminal.integrated.gpuAcceleration)` value of `auto` tries the WebGL renderer and if it failed will fall back to the DOM renderer. When on Linux VMs, browsers that don't support WebGL, or machines with outdated drivers, WebGL may not work properly.
170
170
171
171
### Custom glyphs
172
172
@@ -176,7 +176,7 @@ Below are some examples of these characters with custom line height and letter s
176
176
177
177

178
178
179
-
This feature can be disabled by setting `"terminal.integrated.customGlyphs": false`.
179
+
This feature can be disabled by setting `setting(terminal.integrated.customGlyphs)` to `false`.
180
180
181
181
### Rescaling ambiguous width glyphs
182
182
@@ -200,7 +200,7 @@ Some prompts like [Starship](https://starship.rs/) and [oh-my-posh](https://ohmy
200
200
201
201
### Why is my terminal showing a multi-colored triangle or a black rectangle?
202
202
203
-
The terminal can have problems with GPU accelerated rendering in some environments. For example, you might see a big multi-colored triangle instead of text. This is typically caused by driver/VM graphics issues and the same also happens in Chromium. Work around these issues by launching `code` with the `--disable-gpu` flag or by using the setting `"terminal.integrated.gpuAcceleration": "off"` to avoid using the canvas in the terminal. See the [GPU acceleration](#gpu-acceleration) section for more information.
203
+
The terminal can have problems with GPU accelerated rendering in some environments. For example, you might see a big multi-colored triangle instead of text. This is typically caused by driver/VM graphics issues and the same also happens in Chromium. Work around these issues by launching `code` with the `--disable-gpu` flag or by setting `setting(terminal.integrated.gpuAcceleration)` to `off` to avoid using the canvas in the terminal. See the [GPU acceleration](#gpu-acceleration) section for more information.
204
204
205
205
### Why are the colors in the terminal not correct?
0 commit comments