{"id":6361,"date":"2020-12-17T12:38:43","date_gmt":"2020-12-17T20:38:43","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/commandline\/?p=6361"},"modified":"2020-12-17T12:38:43","modified_gmt":"2020-12-17T20:38:43","slug":"getting-started-with-windows-terminal","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/commandline\/getting-started-with-windows-terminal\/","title":{"rendered":"Getting Started with Windows Terminal"},"content":{"rendered":"

Installation<\/h2>\n

Windows Terminal is available in two different builds: Windows Terminal<\/a> and Windows Terminal Preview<\/a>. Both builds are available for download from the Microsoft Store and from the GitHub releases page<\/a>.<\/p>\n

Requirements<\/h3>\n

In order to run either Windows Terminal build, your machine must be on Windows 10 1903 or later.<\/p>\n

Windows Terminal Preview<\/h3>\n

Windows Terminal Preview is the build where new features arrive first. This build is intended for those who like to see the latest features as soon as they are released. This build has a monthly release cadence with the newest features each month.<\/p>\n

\"Image<\/a><\/p>\n

Windows Terminal<\/h3>\n

Windows Terminal is the main build for the product. Features that arrive in Windows Terminal Preview appear in Windows Terminal after a month of being in production. This allows for extensive bug testing and stabilization of new features. This build is intended for those who want to receive features after they have been introduced and tested by the Preview community.<\/p>\n

First launch<\/h2>\n

After installing the terminal, you can launch the app and get started right away with the command line. By default, the terminal includes Windows PowerShell, Command Prompt, and Azure Cloud Shell profiles inside the dropdown. If you have Windows Subsystem for Linux (WSL) distributions installed on your machine, they should also dynamically populate as profiles when you first launch the terminal.<\/p>\n

Profiles<\/h2>\n

Profiles act as different command line environments that you can configure inside the terminal. By default, each profile uses a different command line executable, however you can create as many profiles as you’d like using the same executable. Each profile can have its own customizations to help you differentiate between them and add your own flair to each one.<\/p>\n

\"Image<\/a><\/p>\n

Default profile<\/h3>\n

Upon first launch of Windows Terminal, the default profile is set to Windows PowerShell. The default profile is the profile that always opens when you launch the terminal and it is the profile that will open when clicking the new tab button. You can change the default profile by setting \"defaultProfile\"<\/code> to the name of your preferred profile in your settings.json file.<\/p>\n

\"defaultProfile\": \"PowerShell\"\n<\/code><\/pre>\n
Adding a new profile<\/h3>\n
New profiles can be added dynamically by the terminal or by hand. Windows Terminal will create profiles for PowerShell and WSL distributions automatically. These profiles will have a \"source\"<\/code> property that tells the terminal where it can find the proper executable.<\/p>\n
If you’d like to create a new profile by hand, you just need to generate a new \"guid\"<\/code><\/a>, provide a \"name\"<\/code>, and provide the executable for the \"commandline\"<\/code> property.<\/p>\n
\ud83d\udc49 Note:<\/strong> You will not be able to copy the \"source\"<\/code> property from a dynamically generated profile. The terminal will just ignore this profile. You will have to replace \"source\"<\/code> with \"commandline\"<\/code> and provide the executable in order to duplicate a dynamically generated profile.<\/p>\n
Settings.json structure<\/h2>\n
There are two settings files included in Windows Terminal. One is defaults.json, which can be opened by holding the Alt<\/kbd> key and clicking the Settings button in the dropdown. This is an unchangeable file that includes all of the default settings that come with the terminal. The second file is settings.json, which is where you can apply all of your custom settings. This can be accessed by clicking the Settings button in the dropdown menu.<\/p>\n
The settings.json file is split into four main sections. The first is the global settings<\/a> object, which lives at the top of the JSON file inside the first {<\/code>. Settings applied here will affect the entire application.<\/p>\n
Looking down the file, the next main section is the \"profiles\"<\/code> object. The \"profiles\"<\/code> object is split into two sections: \"defaults\"<\/code> and \"list\"<\/code>. You can apply profile settings<\/a> to the \"defaults\"<\/code> object and these will apply to all profiles in your \"list\"<\/code>. The \"list\"<\/code> contains each profile object that represents the profiles described above and these are the items that appear in your terminal’s dropdown menu. Settings applied to individual profiles in the \"list\"<\/code> will override settings applied in the \"defaults\"<\/code> section.<\/p>\n
Further down in the file is the \"schemes\"<\/code> array. This is where custom color schemes<\/a> can be placed. A great tool to help you generate your own color schemes is terminal.sexy<\/a>.<\/p>\n
Lastly, at the bottom of the file, lives the \"actions\"<\/code> array. Objects listed here add actions<\/a> to your terminal, which can be invoked by the keyboard and\/or found inside the command palette<\/a>.<\/p>\n
Basic customizations<\/h2>\n
Here are some basic settings to get you started with customizing your terminal.<\/p>\n
Background image<\/h3>\n
One of our most popular settings is the custom background image. This is a profile<\/em> setting, so it can either be placed inside the \"defaults\"<\/code> object inside the \"profiles\"<\/code> object to apply to all profiles or inside a specific profile object.<\/p>\n
\"backgroundImage\": \"C:\\Users\\admin\\background.png\"\n<\/code><\/pre>\n
The \"backgroundImage\"<\/code> setting accepts the file location of the image you would like to use as your profile background. Accepted file types include .jpg, .png, .bmp, .tiff, .ico, and .gif.<\/p>\n
\"Image<\/a><\/p>\n
Color scheme<\/h3>\n
The list of available color schemes can be found on our docs site<\/a>. Color schemes are applied at the profile<\/em> level, so you can place the setting inside \"defaults\"<\/code> or in a specific profile object.<\/p>\n
\"colorScheme\": \"COLOR SCHEME NAME\"\n<\/code><\/pre>\n
This setting accepts the name of the color scheme. You can also create your own color scheme and place it inside the \"schemes\"<\/code> list, then set the profile setting to the name of that new scheme to apply it.<\/p>\n
Font face<\/h3>\n
By default, Windows Terminal uses Cascadia Mono as its font face. The font face is a profile<\/em> level setting. You can change your font face by setting \"fontFace\"<\/code> to the name of the font you would like to use.<\/p>\n
\"fontFace\": \"FONT NAME\"`\n<\/code><\/pre>\n
\ud83d\udca1 Tip:<\/strong> Windows Terminal also ships with the Cascadia Code font face, which includes programming ligatures (see gif below). If you are using Powerline, Cascadia Code also comes in a PL version which can be downloaded from GitHub<\/a>.<\/p>\n
\"\"<\/a><\/p>\n
Great resources<\/h2>\n
\ud83c\udf1f Windows Terminal documentation<\/a><\/p>\n
\ud83c\udf1f How to make a pretty prompt in Windows Terminal with Powerline, Nerd Fonts, Cascadia Code, WSL, and oh-my-posh by Scott Hanselman<\/a><\/p>\n
\ud83c\udf1f How to set up an awesome prompt with your Git Branch, Windows Terminal, PowerShell, + Cascadia Code! by Scott Hanselman<\/a><\/p>\n
\ud83c\udf1f Windows Terminal Feature PREVIEW – Customize your keybindings, color tabs, split panes, and MORE! by Scott Hanselman<\/a><\/p>\n
\ud83c\udf1f >_TerminalSplash – Windows Terminal themes<\/a><\/p>\n
Cheers<\/h2>\n
We hope this post helped you get set up with Windows Terminal! If you have any questions, feel free to reach out to Kayla (@cinnamon_msft<\/a>) on Twitter. If you have any feature requests or find any bugs, you can file an issue on GitHub<\/a>. Our next release is planned for January, so we will see you then!<\/p>\n
\"Image<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Installation Windows Terminal is available in two different builds: Windows Terminal and Windows Terminal Preview. Both builds are available for download from the Microsoft Store and from the GitHub releases page. Requirements In order to run either Windows Terminal build, your machine must be on Windows 10 1903 or later. Windows Terminal Preview Windows Terminal […]<\/p>\n","protected":false},"author":3539,"featured_media":6363,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[10,1,2,4,1535,5,6,8,9,782],"tags":[27,29,31,48,59,69,70,72],"class_list":["post-6361","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cmd","category-commandline","category-command-line","category-ms-dos","category-open-source","category-windows-10","category-windows-console","category-windows-store","category-bash-on-ubuntu-on-windows","category-windows-terminal","tag-cmd","tag-command-line","tag-console","tag-powershell","tag-terminal","tag-windows","tag-windows-10","tag-wsl"],"acf":[],"blog_post_summary":"
Installation Windows Terminal is available in two different builds: Windows Terminal and Windows Terminal Preview. Both builds are available for download from the Microsoft Store and from the GitHub releases page. Requirements In order to run either Windows Terminal build, your machine must be on Windows 10 1903 or later. Windows Terminal Preview Windows Terminal […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts\/6361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/users\/3539"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/comments?post=6361"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts\/6361\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/media\/6363"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/media?parent=6361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/categories?post=6361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/tags?post=6361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}