Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Main > Live #448

Merged
merged 41 commits into from
Nov 22, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
41 commits
Select commit Hold shift + click to select a range
9b7fa08
Update to change equal symbol to plus key
mattwojo Aug 13, 2021
4f05c9b
change + to plus as shipped by default
mattwojo Aug 13, 2021
4fb927f
Add notes about title change persistance
mattwojo Aug 23, 2021
0c814fd
Update settings.json section
mattwojo Aug 23, 2021
3258a40
Link settings.json mentions
mattwojo Aug 24, 2021
ffa1f52
Fix links
mattwojo Aug 24, 2021
562da65
fix a few more links
mattwojo Aug 24, 2021
b8b7b92
Update TerminalDocs/customize-settings/actions.md
mattwojo Aug 24, 2021
7b7dc13
Update TerminalDocs/dynamic-profiles.md
mattwojo Aug 24, 2021
69ba53b
Update TerminalDocs/customize-settings/actions.md
mattwojo Aug 24, 2021
ab5452d
Remove repititious section
mattwojo Aug 24, 2021
eb0947d
Merge branch 'master' of https://github.com/MicrosoftDocs/terminal
mattwojo Aug 24, 2021
3c47641
Added browser media keys (#371)
FWest98 Aug 30, 2021
cad9089
Add link to what is command line shell video (#377)
mattwojo Aug 30, 2021
8bfe469
add intenseTextStyle to the docs (#381)
zadjii-msft Aug 30, 2021
99626e6
Multiple new pane features (#383)
Rosefield Aug 30, 2021
62bbde6
wt.exe --window argument now available (#388)
Sophismata Aug 30, 2021
dc725cd
Add notes that the `font` object is only 1.10+ (#389)
zadjii-msft Aug 30, 2021
f7f5011
Remove MinimizeToTray action mentions (#387)
leonMSFT Aug 30, 2021
e7f739e
Docs updates for 1.11 release (#397)
cinnamon-msft Aug 31, 2021
0a6bc17
Merge branch 'live' into master
cinnamon-msft Aug 31, 2021
6a2862a
Specify OS version availability for defterm (#417)
carlos-zamora Sep 20, 2021
76f8d9f
Remove tilde
mattwojo Oct 4, 2021
d8e2ed7
Improve dup tab description
mattwojo Oct 4, 2021
e14f4d4
Update minimizetotray setting to new name
cinnamon-msft Oct 5, 2021
aa186ea
Merge release 1.12 into master (#428)
cinnamon-msft Oct 20, 2021
63d1165
Merge branch 'live' into master
cinnamon-msft Oct 20, 2021
c2e0813
Remove preview labels
cinnamon-msft Oct 20, 2021
8674adc
Add redirect for old powerline page
mattwojo Nov 12, 2021
656af92
Merge branch 'live' into master
mattwojo Nov 12, 2021
0232a87
Add vscode to gitignore
mattwojo Nov 12, 2021
a7c11cf
Config changes to reflect the default branch from master to main.
mattwojo Nov 17, 2021
71bd0f6
Add a note about the command palette to this doc (#447)
zadjii-msft Nov 19, 2021
6312ed2
Add details about the command used to print the table (#446)
zadjii-msft Nov 19, 2021
6a12396
initialPos -> initialPosition (#445)
zadjii-msft Nov 19, 2021
0b4abe8
Add tip on extensions for configuration files (#440)
nivaldoh Nov 19, 2021
669763b
Corrected path (#434)
dabide Nov 19, 2021
e2331a9
Update panes.md (#432)
tsathis Nov 19, 2021
f69f709
Correct $PROFILE configuration (#431)
Cutano Nov 19, 2021
e5f99aa
Add a sample page (#444)
mattwojo Nov 22, 2021
a993bb6
Add FAQ page (#442)
mattwojo Nov 22, 2021
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,5 @@ _site/
_themes*/
_repo.*/

.openpublishing.buildcore.ps1
.openpublishing.buildcore.ps1
.vscode/settings.json
6 changes: 3 additions & 3 deletions .openpublishing.publish.config.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,15 +23,15 @@
"sync_notification_subscribers": [],
"branches_to_filter": [],
"git_repository_url_open_to_public_contributors": "https://github.com/MicrosoftDocs/terminal",
"git_repository_branch_open_to_public_contributors": "master",
"git_repository_branch_open_to_public_contributors": "main",
"skip_source_output_uploading": false,
"need_preview_pull_request": true,
"contribution_branch_mappings": {},
"dependent_repositories": [
{
"path_to_root": "_themes",
"url": "https://github.com/Microsoft/templates.docs.msft",
"branch": "master",
"branch": "main",
"branch_mapping": {}
}
],
Expand All @@ -40,4 +40,4 @@
"docs_build_engine": {
"name": "docfx_v3"
}
}
}
7 changes: 6 additions & 1 deletion .openpublishing.redirection.json
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@
"source_path": "TerminalDocs/get-started.md",
"redirect_url": "https://docs.microsoft.com/windows/terminal/install",
"redirect_document_id": true
},
{
"source_path": "TerminalDocs/tutorials/powerline-setup.md",
"redirect_url": "https://docs.microsoft.com/windows/terminal/tutorials/custom-prompt-setup",
"redirect_document_id": true
}
]
}
}
4 changes: 4 additions & 0 deletions TerminalDocs/TOC.yml
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,10 @@
href: custom-terminal-gallery/frosted-glass-theme.md
- name: Retro Command Prompt
href: custom-terminal-gallery/retro-command-prompt.md
- name: FAQs
href: faq.yml
- name: Samples
href: samples.md
- name: Troubleshooting
href: troubleshooting.md

Expand Down
3 changes: 3 additions & 0 deletions TerminalDocs/customize-settings/color-schemes.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,9 @@ ___

Windows Terminal includes these color schemes inside the defaults.json file, which can be accessed by holding <kbd>alt</kbd> and selecting the settings button. Color schemes can **not** be changed in the defaults.json file. For a color scheme to apply across all profiles, change it in the [defaults section of your settings.json file](./profile-general.md).

> [!NOTE]
> You can print the current color scheme to the Terminal using [`colortool`](https://github.com/microsoft/terminal/tree/main/src/tools/ColorTool), with the commandline `colortool -c`


### Campbell

Expand Down
10 changes: 5 additions & 5 deletions TerminalDocs/customize-settings/startup.md
Original file line number Diff line number Diff line change
Expand Up @@ -180,11 +180,11 @@ When set to `true`, the terminal window will auto-center itself on the display i

This interacts with the other launch settings in the following ways:

* `"initialPos": x,y`, `"centerOnLaunch": true`, `"launchMode": "default"`: center on the monitor that `x,y` is on.
* `"initialPos": x,y`, `"centerOnLaunch": true`, `"launchMode": "maximized"`: maximized on the monitor that `x,y` is on (`centerOnLaunch` adds nothing).
* `"initialPos": <omitted>`, `"centerOnLaunch": true`, `"launchMode": "default"`: center on the default monitor.
* `"initialPos": <omitted>`, `"centerOnLaunch": true`, `"launchMode": "focus"`: center and enter focus mode on the default monitor.
* `"initialPos": <omitted>`, `"centerOnLaunch": true`, `"launchMode": "maximized"`: maximized on the default monitor (`centerOnLaunch` adds nothing).
* `"initialPosition": x,y`, `"centerOnLaunch": true`, `"launchMode": "default"`: center on the monitor that `x,y` is on.
* `"initialPosition": x,y`, `"centerOnLaunch": true`, `"launchMode": "maximized"`: maximized on the monitor that `x,y` is on (`centerOnLaunch` adds nothing).
* `"initialPosition": <omitted>`, `"centerOnLaunch": true`, `"launchMode": "default"`: center on the default monitor.
* `"initialPosition": <omitted>`, `"centerOnLaunch": true`, `"launchMode": "focus"`: center and enter focus mode on the default monitor.
* `"initialPosition": <omitted>`, `"centerOnLaunch": true`, `"launchMode": "maximized"`: maximized on the default monitor (`centerOnLaunch` adds nothing).

**Property name:** `centerOnLaunch`

Expand Down
99 changes: 99 additions & 0 deletions TerminalDocs/faq.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
### YamlMime:FAQ
metadata:
title: Windows Terminal FAQ
description: Frequently asked questions about Windows Terminal, such as how to start terminal in administrator mode, how to save a terminal session, and more.
ms.topic: troubleshooting
ms.date: 11/15/2021
ms.author: mattwoj
author: mattwojo
manager: jken
ms.reviewer: cinnamon

title: Windows Terminal FAQ
summary: |
Find answers to some of the most frequently asked questions about Windows Terminal.

sections:
- name: General
questions:
- question: How do I run a shell in Windows Terminal in administrator mode?
answer: |
To run Windows Terminal with elevated administrator permission (admin mode), right-click on the Windows Terminal icon, then again on the Windows Terminal title that displays, then select "Run as administrator".

![Windows Terminal admin mode](./images/admin-mode.png)

Alternatively, you can open the Windows Quick Access menu using the shortcut, ⊞ Windows key + X, and then selecting Windows Terminal (Admin).

- question: Is it possible to mix admin and non-admin tabs in a Windows Terminal window?
answer: |
No, mixing administrator-level permission tabbed shells with those that do not have elevated administrator permission is not supported due to security concerns.

- question: Can I use Windows Terminal as the integrated terminal in VSCode?
answer: |
No, Visual Studio Code is xtermjs and written in TypeScript while Windows Terminal is native code.

- question: What shells does Windows Terminal support?
answer: |
Windows Terminal will support any command line or shell that you have on your machine, including those that are included with Windows like PowerShell or Windows Command Prompt (cmd.exe), as well as any Linux distribution that can be installed with [WSL](/windows/wsl/), Azure Cloud Shell, Git Bash, etc. The terminal will automatically detect when you've installed a Linux distribution with WSL and create a profile for you. It can also save your Azure credentials, so you can quickly log in quickly to Azure Cloud Shell.

- question: How can I manually add a shell?
answer: |
In your [settings.json file](./install.md#settings-json-file), you can create or modify profiles that run any command-line executable. In the settings.json file, set "commandline" to whatever you want. For example, powershell --> "pwsh.exe".
You can also add a profile using the terminal settings ui by scrolling to the bottom of your profiles list and selecting "+ Add a new profile".
![Screenshot of settings add a profile](./images/settings-add-profile.png)

- question: What is the difference between Windows Terminal and Windows Terminal (Preview)?
answer: |
[Windows Terminal](https://www.microsoft.com/p/windows-terminal/9n0dx20hk701?rtc=1&activetab=pivot:overviewtab) is the stable public release and receives regular updates that have been tested and debugged in the preview release. The recommended way to [install](./install.md) is via the Microsoft Store, which will provide automatic updates whenever they are released.
[Windows Terminal Preview](https://www.microsoft.com/p/windows-terminal-preview/9n8g5rfz9xk3#activetab=pivot:overviewtab) is a release for those interested in trying the latest features as they are being developed, tested for bugs, and becoming stable enough to be added to the main terminal release. Features from this release are documented with the (Preview) tag.

- question: What alternative ways are there to install Windows Terminal?
answer: |
While we recommend installing Windows Terminal [using the Microsoft Store](https://www.microsoft.com/p/windows-terminal/9n0dx20hk701?rtc=1&activetab=pivot:overviewtab), you can also install using [Windows Package Manager](https://github.com/Microsoft/terminal#via-windows-package-manager-cli-aka-winget), [GitHub](https://github.com/Microsoft/terminal#via-github), [Chocolatey](https://github.com/Microsoft/terminal#via-chocolatey-unofficial), or [Scoop](https://github.com/Microsoft/terminal#via-scoop-unofficial).

- question: Is it possible to initialize a Windows Terminal profile with a batch file?
answer: |
Yes. You first need to go to the [Profiles](./customize-settings/profile-general.md) section of your [settings.json file](./install.md#settings-json-file). Using the [`"commandline":` property](./customize-settings/profile-general.md#command-line), you can specify any batch file, command, ssh connection, or executable that you want to run as a profile in Windows Terminal. You just need to enter the path to the file that you want to run.

This example shows an example of a terminal profile set up based on a "demo" batch file.

```json
{
"commandline": "%USERPROFILE%/OneDrive/demo.bat",
"name": "Batch Profile"
}
```
This can also be done in the Settings UI. Select "+ Add a new profile" > "+ New empty profile". Browse to the starting directory where your batch file (or SSH connection, executable, command file, etc) is located. Give the profile a name and save.
![Screenshot of settings add an batch file profile](./images/settings-batch-file.png)

- question: What sort of features have open-source community contributors added to Windows Terminal?
answer: |
There have been a wide variety of [contributions](https://github.com/microsoft/terminal/pulls?q=is%3Apr+is%3Aclosed) to Windows Terminal, including bug fixes, identifying and discussing [issues](https://github.com/microsoft/terminal/issues), [contributing to this documentation](/contribute/), but a few of our favorite features that have come from community contributions have included support for [background images and gifs](./customize-settings/profile-appearance.md#background-images-and-icons), [retro effects](./customize-settings/profile-appearance.md#retro-terminal-effects), and [tab coloring](./customize-settings/profile-appearance.md#tab-color), just to name a few. Learn more about [how to contribute](https://github.com/microsoft/terminal/blob/main/CONTRIBUTING.md).

- question: What is conhost.exe?
answer: |
The Windows Console host, conhost.exe, is Windows' original command-line user experience. It also hosts Windows' command-line infrastructure and the Windows Console API server, input engine, rendering engine, user preferences, etc. A primary goal of Windows Console is to maintain backward compatibility, thus adding new features became prohibitive and let to the creation of the Windows Terminal. Learn more in the [Windows Terminal open-source repo](https://github.com/Microsoft/terminal#the-windows-console-host) and in the [WIndows Console docs](/windows/console/definitions#console-host).

- question: Can I save the layout of all of my open console windows when closing Windows Terminal and restore them when starting a new session?
answer: |
Yes! As of [Windows Terminal Preview v1.12.2922.0](https://github.com/microsoft/terminal/releases/tag/v1.12.2922.0), you can now save window pane layouts upon closing a terminal session with the [firstWindowPreference](./customize-settings/startup.md#behavior-when-starting-a-new-terminal-session-preview) global setting.

- question: What is being planned for Windows Terminal? Is there a development roadmap or feature request list that I can contribute to?
answer: |
Windows Terminal is under very active development. You can view the team's plans on the [Terminal 2.0 Roadmap](https://github.com/microsoft/terminal/blob/main/doc/terminal-v2-roadmap.md) document in the open-source terminal repo. New features go into [Windows Terminal Preview](https://aka.ms/terminal-preview) first, then typically a month after they've been in Preview, those features move into [Windows Terminal](https://aka.ms/terminal).

You can contribute feature Requests or ideas, as well as bug reports, security vulnerabilities, or documentation issues by [filing an issue in the terminal repo](https://github.com/microsoft/terminal/issues/new/choose).

![Screenshot of filing an issue in terminal repo](./images/file-issue.png)

# - question: Is there a way to sync your terminal settings across devices?
# answer: |
# TBD

# - question: Can we expect a status bar on the bottom of Windows Terminal?
# answer: |
# TBD

# - question: TBD
# answer: |
# TBD
Binary file added TerminalDocs/images/admin-mode.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added TerminalDocs/images/file-issue.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added TerminalDocs/images/settings-add-profile.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added TerminalDocs/images/settings-batch-file.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added TerminalDocs/images/terminalretro.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 2 additions & 1 deletion TerminalDocs/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,8 @@ The path for your Windows Terminal settings.json file may be found in one of the
- Terminal (unpackaged: Scoop, Chocolately, etc): `%LOCALAPPDATA%\Microsoft\Windows Terminal\settings.json`

> [!Tip]
> You can access the default settings for Windows Terminal by selecting **Settings** in the dropdown menu while holding <kbd>Alt</kbd> to open the `defaults.json` file in your default text editor. This file is auto-generated and any changes to it will be ignored.
> 1. You can access the default settings for Windows Terminal by selecting **Settings** in the dropdown menu while holding <kbd>Alt</kbd> to open the `defaults.json` file in your default text editor. This file is auto-generated and any changes to it will be ignored.
> 2. It is possible to create a [JSON fragment extension](./json-fragment-extensions.md) in order to store profile data and color schemes in a separate file, which can be useful to prevent excessively large configuration files.

## Command line arguments

Expand Down
2 changes: 1 addition & 1 deletion TerminalDocs/json-fragment-extensions.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,6 @@ The first is that the installation is for all the users on the system. In this c

In the second case, the installation is only for the current user. In this case, the JSON files should be added to the folder:

`C:\Users\<user>\AppData\Local\Microsoft\Windows Terminal\Fragments\{file-name}.json`
`C:\Users\<user>\AppData\Local\Microsoft\Windows Terminal\Fragments\{app-name}\{file-name}.json`

Note that both the `ProgramData` and `LocalAppData` folders are known folders that the installer should be able to access. If in either case, if the `Windows Terminal\Fragments` directory does not exist, the installer should create it. The `{app-name}` should be unique to your application and the `{file-name}.json` can be anything - the terminal will read all .json files in that directory.
6 changes: 5 additions & 1 deletion TerminalDocs/panes.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Panes give you the ability to run multiple command-line applications next to eac

### Using the keyboard

You can either create a new vertical or horizontal pane in Windows Terminal. Splitting vertically will open a new pane to the right of the focused pane and splitting horizontally will open a new pane below the focused pane. Using directional splits `up`, `right`, `down`, or `left` gives more options for where the new pane can go. `right` and `down` are equivalent to `vertical` and `horizontal`, whereas `up` and `left` allow you to put the new pane above and to the left of the focused pane respectively. To create a new vertical pane of your default profile, you can press the <kbd>Alt</kbd>+<kbd>Shift</kbd>+plus key combination. For a horizontal pane of your default profile, you can use <kbd>Alt</kbd>+<kbd>Shift</kbd>+<kbd>-</kbd>.
You can either create a new vertical or horizontal pane in Windows Terminal. Splitting vertically will open a new pane to the right of the focused pane and splitting horizontally will open a new pane below the focused pane. Using directional splits `up`, `right`, `down`, or `left` gives more options for where the new pane can go. `right` and `down` are equivalent to `vertical` and `horizontal`, whereas `up` and `left` allow you to put the new pane above and to the left of the focused pane respectively. To create a new vertical pane of your default profile, you can press the <kbd>Alt</kbd>+<kbd>Shift</kbd>+<kbd>+</kbd> key combination. For a horizontal pane of your default profile, you can use <kbd>Alt</kbd>+<kbd>Shift</kbd>+<kbd>-</kbd>.

![Windows Terminal create pane](./images/open-panes.gif)
_Configuration: [Raspberry Ubuntu](./custom-terminal-gallery/raspberry-ubuntu.md)_
Expand Down Expand Up @@ -201,6 +201,10 @@ You can zoom the focused pane to fill the entire contents of the window.

![Windows Terminal toggle pane zoom](./images/toggle-pane-zoom.gif)


> [!NOTE]
> The menu in the above gif is the [Command Palette](./command-palette.md), which can be opened with <kbd>Ctrl+Shift+P</kbd> by default.

This can be done by using the `togglePaneZoom` command.

```json
Expand Down
Loading