naxbubble.blogg.se

json can be anything - the terminal will read all.

Here is an example of a json file that adds a new profile, modifies an existing profile, and creates a new color scheme. The JSON file should be split up into 2 lists, one for profiles and one for schemes. They can also be used to add new color schemes to users' settings.

If you wanted to get fancy and use PowerShell ISE to find the PowerShell Core guid, you could also use the following code, at the NAME: prompt, type powershell 6.JSON fragment extensions are snippets of JSON that application developers can write to add new profiles to users' settings, or even modify certain existing profiles. You will use the highlighted portion of the string.Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\DAFA0C9613B26094DB3D0861ADDA28CB The ”Production” item, in the form of C:\WINDOWS\Installer\ \PowerShellExe.ico is what you want. The location for the PowerShell Core terminal is noted below. The 'Name' field must be .settings for Windows Terminal to be able to detect the extension. You will use the highlighted portion of the string, leaving out the CN=.Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateRepository\Cache\PackageFamily\Data\7dĬomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateRepository\Cache\PackageFamily\Data\7e The ”Publisher” item, in the form of CN= 45FBC5C5-8DE5-4E85-AE6A-377002DA7605 is what you want. The location for the WSL terminals is noted below. The registry locations will vary for the different terminals, so you are going to have to search for them using the FIND or FIND NEXT tools under the EDIT menu. The quickest way to find the guid(s) that you will want to add is to use the Registry Editor to search for them.

The guid for each terminal will be different and must be used when adding the code block to the PROFILES.JSON file to allow the Windows Terminal to find the terminal and insert it as a tabbed terminal window.