starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request - Implement Settings UI #2141

New Issue
Closed
opened 2026-01-30 22:47:54 +00:00 by claunia · 59 comments
claunia commented 2026-01-30 22:47:54 +00:00
Owner
Copy Link

Originally created by @cinnamon-msft on GitHub (Jun 24, 2019).

Originally assigned to: @carlos-zamora, @cinnamon-msft, @leonMSFT on GitHub.

Summary of the new feature/enhancement

Implement a Settings UI for Windows Terminal. This UI should read from and update the settings.json file. The user should still be able to edit the JSON directly, if so desired.

Spec & Design: #6720

Implementation Plan

By @carlos-zamora. We're working off of the feature/settings-ui branch. It runs the same CI as master. The idea is that you make PRs targeting feature/settings-ui and when the Settings UI is ready for delivery, we merge it into master.

We're basically starting with #7370.

Back-end

These work items generally won't touch any UI or XAML.

  • #885 - TerminalSettingsModel
  • Write settings to JSON
    • Part 1: JsonUtils includes ConversionTrait, which is used to convert settings from JSON to our settings objects (FromJson()). We should be able to introduce a ToJson() function to ConversionTrait. This will mainly handle individual settings being converted to their enum value. (PR #7609)
    • Part 2: Introduce ToJson() as a function on full settings objects (i.e: Profile, GlobalAppSettings, etc...) (PR #8018)
    • Part 3: Layer the output JSON from part 2, onto the user's existing settings. We need to make sure we don't overwrite any comments placed by the user.
  • Update openSettings command to open the Settings UI

Middle-end

These work items may touch a bit of the XAML. You'll have to touch the TerminalSettingsEditor project, but you won't be too caught up in the polish of icons, margins, etc.

  • Embed the Settings UI as a tab in Windows Terminal (TerminalApp)
  • Replace ObjectModel objects in the prototype with real TerminalSettingsModel object references
  • Data Bind the settings to the TerminalSettingsModel
    • Global Settings
    • Profiles:
      • List of profiles --> Navigation bar
      • Profile settings
    • Color Schemes:
      • List of color schemes --> dropdown menu
      • colors
    • Key Bindings

Miscellaneous Follow-Ups from PRs

  • Use the same UI for a new profile and existing profile.
  • ColorSchemes.xaml button color flyouts should be all in a single control.
  • Ensure all strings are attached to UIDs. (PR #7833 )
  • Commandline handling needs to be robust and intelligent.
  • Push localizable strings into a Resources.resw (PR #7833)
  • Dedupe Utils's GetFontIcon function with Command's magic icon handler as per #7802
  • Hide warning, and change save/reset buttons to apply/discard (PR #8082 )
    • we don't have a system to detect changes yet, so this'll do in the meantime.

Front-end

These work items include a bit more design work. Make sure you look at the mockups in #6720.

  • Update icons (PR #8013)
    • Profiles: E756
    • Appearance: E771
    • Color Schemes: E790
    • Startup: E7B5
  • Hook up button to open the JSON settings (see #5915) (PR #8059)
  • Add and hook up "Save" button

Bonus Points

  • Search for settings
  • Home Page
  • Image preview for icons and background image
  • Embed a Terminal Control in the "Appearance" page for profiles
    • This should live update with changes you make to colors, background image, font, etc.
    • Requires a new Terminal Connection specifically designed for this (or even throw a fully operational terminal in there, sure!)
  • Tab title changes depending on what SUI page is currently open.
  • Implement the Keyboard page (key bindings)
    • See #6720 for more details

Bugs

These are bugs that the team is finding as we selfhost the feature branch. This method will be used until the feature branch gets merged into master. At that point, we'll submit bugs normally.

  • TSM and TSE localization not appearing
    • More info: Build authoring error: add <Import Project="$(SolutionDir)build\rules\CollectWildcardResources.targets" /> to TSM and TSE vcxproj (PR #7966 #7967 )
  • The "unsaved changes" thing obstructs the settings at the bottom of the page, and they can't be scrolled up
  • Unlocalized strings:
    • "Settings" on SettingsTab (PR #8012 )
    • "Global" in UI Nav Menu (under Profiles)
      • This string already has a uuid and is defined in the resw. Need to explore deeper.
  • If string for save/reset button is too long, it is cropped (PR #8082 )
  • Spacing is incorrect on the Profiles - Global - Advanced page (PR #8065)
  • Hide keyboard page for 1.5 release (PR #8078)
  • Hide home page for 1.5 release (PR #8078 )

Designs

By @cinnamon-msft. Content within these designs is not final and will be modified. They're simply here for demonstration.

navigation-2

appearance

Originally created by @cinnamon-msft on GitHub (Jun 24, 2019). Originally assigned to: @carlos-zamora, @cinnamon-msft, @leonMSFT on GitHub. # Summary of the new feature/enhancement Implement a Settings UI for Windows Terminal. This UI should read from and update the settings.json file. The user should still be able to edit the JSON directly, if so desired. Spec & Design: #6720 # Implementation Plan By @carlos-zamora. We're working off of the `feature/settings-ui` branch. It runs the same CI as `master`. The idea is that you make PRs targeting `feature/settings-ui` and when the Settings UI is ready for delivery, we merge it into `master`. We're basically starting with #7370. ## Back-end These work items generally won't touch _any_ UI or XAML. - [X] #885 - TerminalSettingsModel - This is needed to be able to access the contents of the settings file. The settings objects must be COM objects. They can then be exposed to a Settings UI to read and modify Windows Terminal's settings. (PR #7667, #7830) - Spec: #6904 - [x] Write settings to JSON - [x] **Part 1**: JsonUtils includes `ConversionTrait`, which is used to convert settings from JSON to our settings objects (`FromJson()`). We should be able to introduce a `ToJson()` function to `ConversionTrait`. This will mainly handle individual settings being converted to their enum value. (PR #7609) - [x] **Part 2**: Introduce `ToJson()` as a function on full settings objects (i.e: Profile, GlobalAppSettings, etc...) (PR #8018) - [ ] **Part 3**: Layer the output JSON from part 2, onto the user's existing settings. We need to make sure we don't overwrite any comments placed by the user. - [x] Update `openSettings` command to open the Settings UI - Spec: #5915 - PR: #7802 ## Middle-end These work items may touch a bit of the XAML. You'll have to touch the `TerminalSettingsEditor` project, but you won't be too caught up in the polish of icons, margins, etc. - [x] Embed the Settings UI as a tab in Windows Terminal (TerminalApp) - Convert `TerminalSettingsEditor` into a DLL - Throw that `TerminalSettingsEditor` into a tab for Terminal - Bonus Points: we should probably only have one Settings UI open at a time - PRs: #7675, #7802 - [x] Replace `ObjectModel` objects in the prototype with real `TerminalSettingsModel` object references - [x] Data Bind the settings to the `TerminalSettingsModel` - Global Settings - Profiles: - List of profiles --> Navigation bar - Profile settings - Color Schemes: - List of color schemes --> dropdown menu - colors - Key Bindings #### Miscellaneous Follow-Ups from PRs - [x] Use the same UI for a new profile and existing profile. - [x] `ColorSchemes.xaml` button color flyouts should be all in a single control. - [x] Ensure all strings are attached to UIDs. (PR #7833 ) - [x] Commandline handling needs to be robust and intelligent. - [x] Push localizable strings into a `Resources.resw` (PR #7833) - [x] Dedupe `Utils`'s `GetFontIcon` function with `Command`'s magic icon handler as per #7802 - [X] Hide warning, and change save/reset buttons to apply/discard (PR #8082 ) - we don't have a system to detect changes yet, so this'll do in the meantime. ## Front-end These work items include a bit more design work. Make sure you look at the mockups in #6720. - [X] Update icons (PR #8013) - Profiles: E756 - Appearance: E771 - Color Schemes: E790 - Startup: E7B5 - [X] Hook up button to open the JSON settings (see #5915) (PR #8059) - [x] Add and hook up "Save" button ## Bonus Points - [ ] Search for settings - [ ] Home Page - [ ] Image preview for icons and background image - [ ] Embed a Terminal Control in the "Appearance" page for profiles - This should live update with changes you make to colors, background image, font, etc. - Requires a new Terminal Connection specifically designed for this (or even throw a fully operational terminal in there, sure!) - [ ] Tab title changes depending on what SUI page is currently open. - [ ] Implement the Keyboard page (key bindings) - See #6720 for more details ## Bugs These are bugs that the team is finding as we selfhost the feature branch. This method will be used until the feature branch gets merged into master. At that point, we'll submit bugs normally. - [x] TSM and TSE localization not appearing - More info: Build authoring error: add `<Import Project="$(SolutionDir)build\rules\CollectWildcardResources.targets" />` to TSM and TSE vcxproj (PR #7966 #7967 ) - [x] The "unsaved changes" thing obstructs the settings at the bottom of the page, and they can't be scrolled up - [ ] Unlocalized strings: - [X] "Settings" on `SettingsTab` (PR #8012 ) - [ ] "Global" in UI Nav Menu (under Profiles) - This string already has a uuid and is defined in the resw. Need to explore deeper. - [X] If string for save/reset button is too long, it is cropped (PR #8082 ) - [X] Spacing is incorrect on the Profiles - Global - Advanced page (PR #8065) - [x] Hide keyboard page for 1.5 release (PR #8078) - [x] Hide home page for 1.5 release (PR #8078 ) # Designs By @cinnamon-msft. Content within these designs is not final and will be modified. They're simply here for demonstration. ![navigation-2](https://user-images.githubusercontent.com/48369326/87360352-cbf8ea80-c51e-11ea-9346-02f1ea8fd169.png) ![appearance](https://user-images.githubusercontent.com/48369326/87360362-d0bd9e80-c51e-11ea-9a57-eed9c3608029.png)
claunia commented 2026-01-30 22:47:56 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 25, 2019):

Before anyone asks, yes the plan includes having a good live preview of things that could reasonably be expected to be seen in a terminal.

@DHowett-MSFT commented on GitHub (Jun 25, 2019): Before anyone asks, _yes_ the plan includes having a good live preview of things that could reasonably be expected to be seen in a terminal.
claunia commented 2026-01-30 22:47:56 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Jun 25, 2019):

How would you move between different profile's settings?

Perhaps you could implement a ComboBox in the left NavigationPane to choose a Profile, to which the settings would apply?

image
Your Phone does this

image

Even if you decide not to use Acrylic for the Settings' NavigaitonView Pane, could you please Extend the Title Bar so the navigation view touches the top of the window?

image

image

image

@mdtauk commented on GitHub (Jun 25, 2019): How would you move between different profile's settings? Perhaps you could implement a ComboBox in the left NavigationPane to choose a Profile, to which the settings would apply? ![image](https://user-images.githubusercontent.com/7389110/60066758-03bca680-9700-11e9-82a0-9c48e93e1f52.png) _Your Phone does this_ ![image](https://user-images.githubusercontent.com/7389110/60066827-2b137380-9700-11e9-95bb-7596d9fdf0ef.png) ---- Even if you decide not to use Acrylic for the Settings' NavigaitonView Pane, could you please Extend the Title Bar so the navigation view touches the top of the window? ![image](https://user-images.githubusercontent.com/48369326/60053858-ce777080-968d-11e9-8954-6a57f82f1316.png) ![image](https://user-images.githubusercontent.com/7389110/60066999-d7555a00-9700-11e9-88c3-30c780d57bfc.png) ![image](https://user-images.githubusercontent.com/7389110/60067066-1388ba80-9701-11e9-8f07-13b8e9212cdf.png)
claunia commented 2026-01-30 22:47:56 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Jun 25, 2019):

The plan at the moment is to have a profiles item in the menu on the left and a drop down of all your profiles in the main content area, with fields populated according to the JSON properties and a preview window to show your updated settings.
We don't have mocks of this just yet 😊

@cinnamon-msft commented on GitHub (Jun 25, 2019): The plan at the moment is to have a profiles item in the menu on the left and a drop down of all your profiles in the main content area, with fields populated according to the JSON properties and a preview window to show your updated settings. We don't have mocks of this just yet 😊
claunia commented 2026-01-30 22:47:56 +00:00
Author
Owner
Copy Link

@mikemaccana commented on GitHub (Jul 2, 2019):

Regarding color schemes: per #1750, all iTerm2 color schemes have been ported to Windows Terminal.

@mikemaccana commented on GitHub (Jul 2, 2019): Regarding color schemes: per #1750, **[all iTerm2 color schemes have been ported to Windows Terminal](https://github.com/mbadolato/iTerm2-Color-Schemes/blob/master/windowsterminal)**.
claunia commented 2026-01-30 22:47:56 +00:00
Author
Owner
Copy Link

@DavidLiedle commented on GitHub (Jul 7, 2019):

To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system.

@DavidLiedle commented on GitHub (Jul 7, 2019): To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system.
claunia commented 2026-01-30 22:47:57 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Jul 7, 2019):

To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system.

It should open the profiles.json file, which allows you to change the settings - but eventually there will be a GUI for this file.

@mdtauk commented on GitHub (Jul 7, 2019): > To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system. It _**should**_ open the profiles.json file, which allows you to change the settings - but eventually there will be a GUI for this file.
claunia commented 2026-01-30 22:47:57 +00:00
Author
Owner
Copy Link

@aguywithcode commented on GitHub (Jul 26, 2019):

To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system.

It should open the profiles.json file, which allows you to change the settings - but eventually there will be a GUI for this file.

When I click the settings menu option, it has no effect. I'm using the preview from the windows store. Should I download and build instead?

@aguywithcode commented on GitHub (Jul 26, 2019): > > To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system. > > It _**should**_ open the profiles.json file, which allows you to change the settings - but eventually there will be a GUI for this file. When I click the settings menu option, it has no effect. I'm using the preview from the windows store. Should I download and build instead?
claunia commented 2026-01-30 22:47:57 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Jul 26, 2019):

When I click the settings menu option, it has no effect. I'm using the preview from the windows store. Should I download and build instead?

It should open the profiles.json file inside your default editor for json files. Perhaps you don't have a default set within Windows?

@cinnamon-msft commented on GitHub (Jul 26, 2019): > > When I click the settings menu option, it has no effect. I'm using the preview from the windows store. Should I download and build instead? It should open the profiles.json file inside your default editor for json files. Perhaps you don't have a default set within Windows?
claunia commented 2026-01-30 22:47:57 +00:00
Author
Owner
Copy Link

@mikemaccana commented on GitHub (Jul 26, 2019):

A new preview build is due on the thirtieth so hold on a little while if you want to test something stable

@mikemaccana commented on GitHub (Jul 26, 2019): A new preview build is due on the thirtieth so hold on a little while if you want to test something stable
claunia commented 2026-01-30 22:47:57 +00:00
Author
Owner
Copy Link

@nullptr-leo commented on GitHub (Jul 26, 2019):

To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system.

It should open the profiles.json file, which allows you to change the settings - but eventually there will be a GUI for this file.

When I click the settings menu option, it has no effect. I'm using the preview from the windows store. Should I download and build instead?

Maybe you should check your default JSON file editor first.

@nullptr-leo commented on GitHub (Jul 26, 2019): > > > To be clear, there is currently (Sunday, July 7, 2019) no Settings functionality at all, correct? Clicking the "Settings" menu item from the triangle drop-down has no effect on my system. > > > > > > It _**should**_ open the profiles.json file, which allows you to change the settings - but eventually there will be a GUI for this file. > > When I click the settings menu option, it has no effect. I'm using the preview from the windows store. Should I download and build instead? Maybe you should check your default JSON file editor first.
claunia commented 2026-01-30 22:47:58 +00:00
Author
Owner
Copy Link

@Fisico commented on GitHub (Aug 16, 2019):

windows_terminal_settings_ui

My idea for a settings UI.
The settings page should be an overlay.
First Page: A full screen splash screen overlay, like windows settings.
Tab “Profiles”: Each profile has its own submenu tab where you can set name, commandline, starting dir, startup parameter, font face, font size, acrylic, opacity, background color or image, font color and icon. The selections should update the preview in real-time.
Tab “General”: This is the settings page with general settings like cursor size, overall font face and font size. Some other settings that are also global should be selected here.
The second submenu of “General” is layout, where you can tweak the buffer size, windows size and position.

With the X next to settings, you close the settings overlay.
With the arrow next to General or Profiles you go back to the Settings “Splash screen”

@Fisico commented on GitHub (Aug 16, 2019): ![windows_terminal_settings_ui](https://user-images.githubusercontent.com/329471/63196266-279fc700-c075-11e9-99f3-d45de73a00f4.png) My idea for a settings UI. The settings page should be an overlay. First Page: A full screen splash screen overlay, like windows settings. Tab “Profiles”: Each profile has its own submenu tab where you can set name, commandline, starting dir, startup parameter, font face, font size, acrylic, opacity, background color or image, font color and icon. The selections should update the preview in real-time. Tab “General”: This is the settings page with general settings like cursor size, overall font face and font size. Some other settings that are also global should be selected here. The second submenu of “General” is layout, where you can tweak the buffer size, windows size and position. With the X next to settings, you close the settings overlay. With the arrow next to General or Profiles you go back to the Settings “Splash screen”
claunia commented 2026-01-30 22:47:58 +00:00
Author
Owner
Copy Link

@egmontkob commented on GitHub (Aug 21, 2019):

https://youtu.be/veqs2WVou9M?t=525 (5 seconds) – Dustin, come on... 😛 😛 😛

@egmontkob commented on GitHub (Aug 21, 2019): https://youtu.be/veqs2WVou9M?t=525 (5 seconds) – Dustin, come on... :stuck_out_tongue: :stuck_out_tongue: :stuck_out_tongue:
claunia commented 2026-01-30 22:47:58 +00:00
Author
Owner
Copy Link

@tamimmirza commented on GitHub (Aug 25, 2019):

windows_terminal_settings_ui

My idea for a settings UI.
The settings page should be an overlay.
First Page: A full screen splash screen overlay, like windows settings.
Tab “Profiles”: Each profile has its own submenu tab where you can set name, commandline, starting dir, startup parameter, font face, font size, acrylic, opacity, background color or image, font color and icon. The selections should update the preview in real-time.
Tab “General”: This is the settings page with general settings like cursor size, overall font face and font size. Some other settings that are also global should be selected here.
The second submenu of “General” is layout, where you can tweak the buffer size, windows size and position.

With the X next to settings, you close the settings overlay.
With the arrow next to General or Profiles you go back to the Settings “Splash screen”

The idea of a setting UI would save a lot of time and effort to customize the terminal, I tried adding a new profile along with personalized settings and it took out quite a chunk of time that included checking on Google on how to do it and to save it (profile.json) and re-launch the terminal to see if it works. If not, then repeat. (Yes I am a noob at manually doing it this way and prefer to have a UI. It's a personal preference shared not by me only but others as well).

The mock UI referenced here, though not polished and missing a few things (including adding background image), is far better than manually editing the json file. This feature is extremely crucial and should be available by the next major preview release or final release as this will enable users to focus on how well the terminal reacts to multiple customizations with changes being previewed.

@tamimmirza commented on GitHub (Aug 25, 2019): > ![windows_terminal_settings_ui](https://user-images.githubusercontent.com/329471/63196266-279fc700-c075-11e9-99f3-d45de73a00f4.png) > > My idea for a settings UI. > The settings page should be an overlay. > First Page: A full screen splash screen overlay, like windows settings. > Tab “Profiles”: Each profile has its own submenu tab where you can set name, commandline, starting dir, startup parameter, font face, font size, acrylic, opacity, background color or image, font color and icon. The selections should update the preview in real-time. > Tab “General”: This is the settings page with general settings like cursor size, overall font face and font size. Some other settings that are also global should be selected here. > The second submenu of “General” is layout, where you can tweak the buffer size, windows size and position. > > With the X next to settings, you close the settings overlay. > With the arrow next to General or Profiles you go back to the Settings “Splash screen” The idea of a setting UI would save a lot of time and effort to customize the terminal, I tried adding a new profile along with personalized settings and it took out quite a chunk of time that included checking on Google on how to do it and to save it (profile.json) and re-launch the terminal to see if it works. If not, then repeat. (Yes I am a noob at manually doing it this way and prefer to have a UI. It's a personal preference shared not by me only but others as well). The mock UI referenced here, though not polished and missing a few things (including adding background image), is far better than manually editing the json file. This feature is extremely crucial and should be available by the next major preview release or final release as this will enable users to focus on how well the terminal reacts to multiple customizations with changes being previewed.
claunia commented 2026-01-30 22:47:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 25, 2019):

At the same time, this is a developer tool. Some amount of manual configuration file editing is to be expected, possibly even as late as 1.0. And you don’t need to relaunch terminal to see the effects of your editing.

@DHowett-MSFT commented on GitHub (Aug 25, 2019): At the same time, this is a developer tool. Some amount of manual configuration file editing is to be expected, possibly even as late as 1.0. And you don’t need to relaunch terminal to see the effects of your editing.
claunia commented 2026-01-30 22:47:59 +00:00
Author
Owner
Copy Link

@Fisico commented on GitHub (Aug 29, 2019):

windows_terminal_settings_ui
My idea for a settings UI.
The settings page should be an overlay.
First Page: A full screen splash screen overlay, like windows settings.
Tab “Profiles”: Each profile has its own submenu tab where you can set name, commandline, starting dir, startup parameter, font face, font size, acrylic, opacity, background color or image, font color and icon. The selections should update the preview in real-time.
Tab “General”: This is the settings page with general settings like cursor size, overall font face and font size. Some other settings that are also global should be selected here.
The second submenu of “General” is layout, where you can tweak the buffer size, windows size and position.
With the X next to settings, you close the settings overlay.
With the arrow next to General or Profiles you go back to the Settings “Splash screen”

The idea of a setting UI would save a lot of time and effort to customize the terminal, I tried adding a new profile along with personalized settings and it took out quite a chunk of time that included checking on Google on how to do it and to save it (profile.json) and re-launch the terminal to see if it works. If not, then repeat. (Yes I am a noob at manually doing it this way and prefer to have a UI. It's a personal preference shared not by me only but others as well).

The mock UI referenced here, though not polished and missing a few things (including adding background image), is far better than manually editing the json file. This feature is extremely crucial and should be available by the next major preview release or final release as this will enable users to focus on how well the terminal reacts to multiple customizations with changes being previewed.

Glad you like it. Yea a background image selection button is missing. But there is room for that..

@Fisico commented on GitHub (Aug 29, 2019): > > ![windows_terminal_settings_ui](https://user-images.githubusercontent.com/329471/63196266-279fc700-c075-11e9-99f3-d45de73a00f4.png) > > My idea for a settings UI. > > The settings page should be an overlay. > > First Page: A full screen splash screen overlay, like windows settings. > > Tab “Profiles”: Each profile has its own submenu tab where you can set name, commandline, starting dir, startup parameter, font face, font size, acrylic, opacity, background color or image, font color and icon. The selections should update the preview in real-time. > > Tab “General”: This is the settings page with general settings like cursor size, overall font face and font size. Some other settings that are also global should be selected here. > > The second submenu of “General” is layout, where you can tweak the buffer size, windows size and position. > > With the X next to settings, you close the settings overlay. > > With the arrow next to General or Profiles you go back to the Settings “Splash screen” > > The idea of a setting UI would save a lot of time and effort to customize the terminal, I tried adding a new profile along with personalized settings and it took out quite a chunk of time that included checking on Google on how to do it and to save it (profile.json) and re-launch the terminal to see if it works. If not, then repeat. (Yes I am a noob at manually doing it this way and prefer to have a UI. It's a personal preference shared not by me only but others as well). > > The mock UI referenced here, though not polished and missing a few things (including adding background image), is far better than manually editing the json file. This feature is extremely crucial and should be available by the next major preview release or final release as this will enable users to focus on how well the terminal reacts to multiple customizations with changes being previewed. Glad you like it. Yea a background image selection button is missing. But there is room for that..
claunia commented 2026-01-30 22:47:59 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Aug 29, 2019):

The Settings UI wouldn't need to cover EVERY setting you can set. Anything that affects the visuals of the app, should be there. A link to open the JSON file should be there. A link to a complete list of settings you can add should be there.

Previews for things like Cursor Shape, Acrylic, Background Images, Colours - would make a lot of sense, so someone can try out color schemes, before committing.

Also as some settings are per profile, and others are app wide - some kind of drop down to choose the profile to be edited, would probably be a good idea.

@mdtauk commented on GitHub (Aug 29, 2019): The Settings UI wouldn't need to cover EVERY setting you can set. Anything that affects the visuals of the app, should be there. A link to open the JSON file should be there. A link to a complete list of settings you can add should be there. Previews for things like Cursor Shape, Acrylic, Background Images, Colours - would make a lot of sense, so someone can try out color schemes, before committing. Also as some settings are per profile, and others are app wide - some kind of drop down to choose the profile to be edited, would probably be a good idea.
claunia commented 2026-01-30 22:47:59 +00:00
Author
Owner
Copy Link

@Fisico commented on GitHub (Aug 29, 2019):

The Settings UI wouldn't need to cover EVERY setting you can set. Anything that affects the visuals of the app, should be there. A link to open the JSON file should be there. A link to a complete list of settings you can add should be there.

Previews for things like Cursor Shape, Acrylic, Background Images, Colours - would make a lot of sense, so someone can try out color schemes, before committing.

Also as some settings are per profile, and others are app wide - some kind of drop down to choose the profile to be edited, would probably be a good idea.

2nd image in my concept shows profiles(on the left side) and the settings for it on the main page.

@Fisico commented on GitHub (Aug 29, 2019): > The Settings UI wouldn't need to cover EVERY setting you can set. Anything that affects the visuals of the app, should be there. A link to open the JSON file should be there. A link to a complete list of settings you can add should be there. > > Previews for things like Cursor Shape, Acrylic, Background Images, Colours - would make a lot of sense, so someone can try out color schemes, before committing. > > Also as some settings are per profile, and others are app wide - some kind of drop down to choose the profile to be edited, would probably be a good idea. 2nd image in my concept shows profiles(on the left side) and the settings for it on the main page.
claunia commented 2026-01-30 22:47:59 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Aug 29, 2019):

2nd image in my concept shows profiles(on the left side) and the settings for it on the main page.

I did a similar mock up a while back :)
terminal_settings

@mdtauk commented on GitHub (Aug 29, 2019): > 2nd image in my concept shows profiles(on the left side) and the settings for it on the main page. > I did a similar mock up a while back :) ![terminal_settings](https://user-images.githubusercontent.com/7389110/63964632-7135dc00-ca8f-11e9-91cd-f342bf38e25a.png)
claunia commented 2026-01-30 22:47:59 +00:00
Author
Owner
Copy Link

@yellow-starburst commented on GitHub (Jan 18, 2020):

I think this would be a major improvement. Could this please be pushed out as soon as possible?

@yellow-starburst commented on GitHub (Jan 18, 2020): I think this would be a major improvement. Could this please be pushed out as soon as possible?
claunia commented 2026-01-30 22:47:59 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 18, 2020):

@yellow-starburst you can generally use our Milestones and Projects view (or the active milestone for any specific issue) to figure that out. A settings UI is not in-plan for version 1.0.

@DHowett-MSFT commented on GitHub (Jan 18, 2020): @yellow-starburst you can generally use our Milestones and Projects view (or the active milestone for any specific issue) to figure that out. A settings UI is not in-plan for version 1.0.
claunia commented 2026-01-30 22:48:00 +00:00
Author
Owner
Copy Link

@pranavgoyanka commented on GitHub (Jan 19, 2020):

I tried to make a small UI for the profiles.json file using Python and Tkinter. While the UI is not very good and doesn't really follow the Windows 10 design scheme (because I am only familiar with those technologies), it does the job of editing the profiles.json file.

If someone wishes, they can check it out here

@pranavgoyanka commented on GitHub (Jan 19, 2020): I tried to make a small UI for the profiles.json file using Python and Tkinter. While the UI is not very good and doesn't really follow the Windows 10 design scheme (because I am only familiar with those technologies), it does the job of editing the profiles.json file. If someone wishes, they can check it out [here](https://github.com/pranavgoyanka/windows-terminal-themer)
claunia commented 2026-01-30 22:48:00 +00:00
Author
Owner
Copy Link

@shmuelie commented on GitHub (Feb 14, 2020):

@DHowett-MSFT while this is not within scope for 1.0, would it not be accepted from external developers for 1.0?

@shmuelie commented on GitHub (Feb 14, 2020): @DHowett-MSFT while this is not within scope for 1.0, would it not be accepted from external developers for 1.0?
claunia commented 2026-01-30 22:48:00 +00:00
Author
Owner
Copy Link

@ShubhamBelwal commented on GitHub (Feb 14, 2020):

@SamuelEnglard external PRs are always welcomes no matter what issue/feature request they're targetting.

@ShubhamBelwal commented on GitHub (Feb 14, 2020): @SamuelEnglard external PRs are always welcomes no matter what issue/feature request they're targetting.
claunia commented 2026-01-30 22:48:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 14, 2020):

Pretty much yea. If you could put something together in the 1.0 timeframe we'd happily accept it, but that might be a tall ask 😝

@zadjii-msft commented on GitHub (Feb 14, 2020): Pretty much yea. If you could put something together in the 1.0 timeframe we'd happily accept it, but that might be a tall ask 😝
claunia commented 2026-01-30 22:48:01 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 14, 2020):

So, this one requires a little caution. Kayla has a vision about what she wants to accomplish, but I think that that's something we can communicate with the public. We're not going to land something for v1.0 at any rate, but I absolutely don't want to discourage community work on this one 😄

@DHowett-MSFT commented on GitHub (Feb 14, 2020): So, this one requires a little caution. Kayla has a vision about what she wants to accomplish, but I think that that's something we can communicate with the public. We're not going to land something for v1.0 at any rate, but I absolutely don't want to discourage community work on this one :smile:
claunia commented 2026-01-30 22:48:01 +00:00
Author
Owner
Copy Link

@shmuelie commented on GitHub (Feb 15, 2020):

My thinking was more that you might not want to spend the time reviewing it to focus on 1.0 things.

@shmuelie commented on GitHub (Feb 15, 2020): My thinking was more that you might not want to spend the time reviewing it to focus on 1.0 things.
claunia commented 2026-01-30 22:48:01 +00:00
Author
Owner
Copy Link

@sharpninja commented on GitHub (Feb 25, 2020):

I think it needs to be four sections:

  • Global Settings

    Shows all common settings, grouped by category. Use tabs to prevent scrolling.

  • Keyboard Schemes

    Allow sets of keyboard shortcutes to be named, tagged and grouped. A button to print a Cheat-Sheet would be awesome.

  • Themes/Visual Schemes

    Rich UI for selecting colors for "Themes" with the ability to select background images, name, tag and group themes, and import/export themes with JSON/YAML. A button to "Variate" would start a new Theme that would be a clone, but two buttons, "Darker"/"Lighter" would darken or lighten the theme incrementally to help create variations for Profiles in a group.

  • Profiles

    Ability to name, tag and group Profiles (groups would be separated in the tab flyout menu to visually organize them). Selecting a them would use a preview of each theme in a carousel. Keyboard schemes would be selected from a drop down. When a Profile is tagged or grouped, it would auto-select a theme and keyboard scheme if matching items exist. Profiles can be exported to JSON.

All exportable JSON could be packaged as nuget archives with a powershell script to import the item to the current user's settings.

@sharpninja commented on GitHub (Feb 25, 2020): I think it needs to be four sections: - Global Settings > Shows all common settings, grouped by category. Use tabs to prevent scrolling. - Keyboard Schemes > Allow sets of keyboard shortcutes to be named, tagged and grouped. A button to print a Cheat-Sheet would be awesome. - Themes/Visual Schemes > Rich UI for selecting colors for "Themes" with the ability to select background images, name, tag and group themes, and import/export themes with JSON/YAML. A button to "Variate" would start a new Theme that would be a clone, but two buttons, "Darker"/"Lighter" would darken or lighten the theme incrementally to help create variations for Profiles in a group. - Profiles > Ability to name, tag and group Profiles (groups would be separated in the tab flyout menu to visually organize them). Selecting a them would use a preview of each theme in a carousel. Keyboard schemes would be selected from a drop down. When a Profile is tagged or grouped, it would auto-select a theme and keyboard scheme if matching items exist. Profiles can be exported to JSON. All exportable JSON could be packaged as nuget archives with a powershell script to import the item to the current user's settings.
claunia commented 2026-01-30 22:48:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 25, 2020):

All of those points seem reasonable except for randomly using NuGet 😄

NuGet archives are just zip files with extra metadata that's really only good and useful for binary distributions of things that need to be built into C++/C#/WinJS/etc. projects moreso than as a generic config export format. JSON is already exportable as-is.

@DHowett-MSFT commented on GitHub (Feb 25, 2020): All of those points seem reasonable except for randomly using NuGet 😄 NuGet archives are just zip files with extra metadata that's really only good and useful for binary distributions of things that need to be built into C++/C#/WinJS/etc. projects moreso than as a generic config export format. JSON is already exportable as-is.
claunia commented 2026-01-30 22:48:02 +00:00
Author
Owner
Copy Link

@sharpninja commented on GitHub (Feb 25, 2020):

All of those points seem reasonable except for randomly using NuGet 😄

It's not random, it's meant to facilitate sharing of settings and profiles using Nuget servers. I'm currently working on an app and website that will be a gallery of Windows Terminal Profiles that people can share to and download from. Getting the data to the config file is easy with JSON, but I want to support many different scenarios, one of which is a completely offline scenario where the user doesn't have to edit any JSON files and can be included as part of the setup of a server or container. To facilitate that, the JSON is encapsulated in Nuget with a PS install and uninstall script that will import/remove the JSON from the config.

@sharpninja commented on GitHub (Feb 25, 2020): > All of those points seem reasonable except for randomly using NuGet 😄 It's not random, it's meant to facilitate sharing of settings and profiles using Nuget servers. I'm currently working on an app and website that will be a gallery of Windows Terminal Profiles that people can share to and download from. Getting the data to the config file is easy with JSON, but I want to support many different scenarios, one of which is a completely offline scenario where the user doesn't have to edit any JSON files and can be included as part of the setup of a server or container. To facilitate that, the JSON is encapsulated in Nuget with a PS install and uninstall script that will import/remove the JSON from the config.
claunia commented 2026-01-30 22:48:02 +00:00
Author
Owner
Copy Link

@shmuelie commented on GitHub (Feb 25, 2020):

To facilitate that, the JSON is encapsulated in Nuget with a PS install and uninstall script that will import/remove the JSON from the config.

So chocolatey? Making a PowerShell cmdlet that creates a chocolatey package of a profile shouldn't be that hard.

@shmuelie commented on GitHub (Feb 25, 2020): > To facilitate that, the JSON is encapsulated in Nuget with a PS install and uninstall script that will import/remove the JSON from the config. So chocolatey? Making a PowerShell cmdlet that creates a chocolatey package of a profile shouldn't be that hard.
claunia commented 2026-01-30 22:48:02 +00:00
Author
Owner
Copy Link

@sharpninja commented on GitHub (Feb 25, 2020):

To facilitate that, the JSON is encapsulated in Nuget with a PS install and uninstall script that will import/remove the JSON from the config.

So chocolatey? Making a PowerShell cmdlet that creates a chocolatey package of a profile shouldn't be that hard.

The idea is for the nuget generation and import to be baked in so that a 3rd party tool isn't necessary

@sharpninja commented on GitHub (Feb 25, 2020): > > To facilitate that, the JSON is encapsulated in Nuget with a PS install and uninstall script that will import/remove the JSON from the config. > > So chocolatey? Making a PowerShell cmdlet that creates a chocolatey package of a profile shouldn't be that hard. The idea is for the nuget generation and import to be baked in so that a 3rd party tool isn't necessary
claunia commented 2026-01-30 22:48:03 +00:00
Author
Owner
Copy Link

@shmuelie commented on GitHub (Feb 25, 2020):

completely offline scenario where the user doesn't have to edit any JSON files and can be included as part of the setup of a server or container

Odds are they're using some 3rd-party tool to do this already, chocolatey being one of the possible options. Integrating with those tools seems the best bet there to me.

@shmuelie commented on GitHub (Feb 25, 2020): > completely offline scenario where the user doesn't have to edit any JSON files and can be included as part of the setup of a server or container Odds are they're using some 3rd-party tool to do this already, chocolatey being one of the possible options. Integrating with those tools seems the best bet there to me.
claunia commented 2026-01-30 22:48:03 +00:00
Author
Owner
Copy Link

@sharpninja commented on GitHub (Feb 25, 2020):

The nuget integration isn't necessary, but would set a good precedent and would also be dogfooding...

@sharpninja commented on GitHub (Feb 25, 2020): The nuget integration isn't _necessary_, but would set a good precedent and would also be dogfooding...
claunia commented 2026-01-30 22:48:03 +00:00
Author
Owner
Copy Link

@SFM61319 commented on GitHub (Apr 28, 2020):

This terminal is a UWP app that uses Fluent design and is highly customizable. Maybe take a look at it and kind of shape Windows Terminal similar to it? I mean, even that terminal looks good (although it is in its early stages).

@SFM61319 commented on GitHub (Apr 28, 2020): [This terminal](https://github.com/felixse/FluentTerminal "Fluent terminal") is a UWP app that uses Fluent design and is highly customizable. Maybe take a look at it and kind of shape Windows Terminal similar to it? I mean, even that terminal looks good (although it is in its early stages).
claunia commented 2026-01-30 22:48:04 +00:00
Author
Owner
Copy Link

@SFM61319 commented on GitHub (Apr 29, 2020):

IMO it would look good if the whole settings app (or page) has a background acrylic just like the Terminal (acrylic that changes according to the acrylic settings set in the settings page)

@SFM61319 commented on GitHub (Apr 29, 2020): IMO it would look good if the whole settings app (or page) has a background acrylic just like the Terminal (acrylic that changes according to the acrylic settings set in the settings page)
claunia commented 2026-01-30 22:48:04 +00:00
Author
Owner
Copy Link

@mikemaccana commented on GitHub (Apr 29, 2020):

Keep in mind that settings panels should be consistent across Windows. You may have feedback about how setting panels should look in Windows, but the Terminal GitHub isn't the best place to discuss them. The place to send thoughts about how settings panels should look in Windows is the Feedback app.

@mikemaccana commented on GitHub (Apr 29, 2020): Keep in mind that settings panels should be consistent across Windows. You may have feedback about how setting panels should look in Windows, but the Terminal GitHub isn't the best place to discuss them. The place to send thoughts about how settings panels should look in Windows is the Feedback app.
claunia commented 2026-01-30 22:48:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 30, 2020):

@russhy I deleted your comment because of the specific language it used violating our code of conduct, not because you think our UI would look like a tablet UI. I don't particularly care what you say so long as you express yourself respectfully.

@DHowett-MSFT commented on GitHub (Apr 30, 2020): @russhy I deleted your comment because of the specific language it used violating our [code of conduct](https://opensource.microsoft.com/codeofconduct/), not because you think our UI would look like a tablet UI. I don't particularly care _what_ you say so long as you express yourself respectfully.
claunia commented 2026-01-30 22:48:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 30, 2020):

@russhy sure thing, sorry about that. 😄

@DHowett-MSFT commented on GitHub (Apr 30, 2020): @russhy sure thing, sorry about that. :smile:
claunia commented 2026-01-30 22:48:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 8, 2020):

A

@ghost commented on GitHub (May 8, 2020): A
claunia commented 2026-01-30 22:48:05 +00:00
Author
Owner
Copy Link

@krezol commented on GitHub (May 25, 2020):

How about defaulting to json file view for the advanced users? That way users will edit settings their way.

@krezol commented on GitHub (May 25, 2020): How about defaulting to json file view for the advanced users? That way users will edit settings their way.
claunia commented 2026-01-30 22:48:05 +00:00
Author
Owner
Copy Link

@Alaboudi1 commented on GitHub (Jun 6, 2020):

This terminal is a UWP app that uses Fluent design and is highly customizable. Maybe take a look at it and kind of shape Windows Terminal similar to it? I mean, even that terminal looks good (although it is in its early stages).

That project is pretty awesome! Even all kinds of fonts render perfectly. It is, unfortunately, slower than Terminal. Hope Terminal gets inspired by that project while remains super snappy!

@Alaboudi1 commented on GitHub (Jun 6, 2020): > [This terminal](https://github.com/felixse/FluentTerminal) is a UWP app that uses Fluent design and is highly customizable. Maybe take a look at it and kind of shape Windows Terminal similar to it? I mean, even that terminal looks good (although it is in its early stages). That project is pretty awesome! Even all kinds of fonts render perfectly. It is, unfortunately, slower than Terminal. Hope Terminal gets inspired by that project while remains super snappy!
claunia commented 2026-01-30 22:48:05 +00:00
Author
Owner
Copy Link

@michael-hawker commented on GitHub (Jun 11, 2020):

🦙 Seems like this could be a good fit for the Form Control Proposal in WinUI.

@michael-hawker commented on GitHub (Jun 11, 2020): 🦙 Seems like this could be a good fit for the [Form Control Proposal in WinUI](https://github.com/microsoft/microsoft-ui-xaml/issues/82).
claunia commented 2026-01-30 22:48:06 +00:00
Author
Owner
Copy Link

@niels9001 commented on GitHub (Jun 13, 2020):

I agree with @michael-hawker - but I think Form Control is still in a proposal stage?

For PowerToys, we've put in quite some effort to get the XAML right: all fontsizes, margins, paddings and other attributes mimic the W10 Settings app. In this way it looks and feels native to Windows and I think it would be great to share the same UX?

I'm happy to contribute by creating all the XAML that is required according to the spec.. and to polish it all up. @zadjii-msft @DHowett . Is there already an active branch?

81483649-0e146000-9240-11ea-86be-1c6e1d56a856

@niels9001 commented on GitHub (Jun 13, 2020): I agree with @michael-hawker - but I think Form Control is still in a proposal stage? For PowerToys, we've put in quite some effort to get the XAML right: all fontsizes, margins, paddings and other attributes mimic the W10 Settings app. In this way it looks and feels native to Windows and I think it would be great to share the same UX? I'm happy to contribute by creating all the XAML that is required according to the spec.. and to polish it all up. @zadjii-msft @DHowett . Is there already an active branch? ![81483649-0e146000-9240-11ea-86be-1c6e1d56a856](https://user-images.githubusercontent.com/9866362/84571770-ca100000-ad95-11ea-9119-8a7de755634c.png)
claunia commented 2026-01-30 22:48:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 15, 2020):

I believe there is a variety of WIP branches, but I honestly don't know which ones are active or not. I believe @carlos-zamora and @cinnamon-msft do know though

@zadjii-msft commented on GitHub (Jun 15, 2020): I believe there is a variety of WIP branches, but I honestly don't know which ones are active or not. I believe @carlos-zamora and @cinnamon-msft _do_ know though
claunia commented 2026-01-30 22:48:06 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jun 15, 2020):

The latest branch is cinnamon/settings-ui-v2. We implemented the Settings UI as a separate app that can be found under src/TerminalSettings.

We're still working on organizing a plan/spec for the Settings UI as a whole, so feel free to clean up the Globals and Color Schemes page for now, or poke around.

For the record, some of the stuff that we still need to plan out are...

  • changes to the Profiles page
  • overall design of the Keybindings page
  • how to sync the JSON and the Settings UI
    We have some ideas, but we'll come out with an actual spec for all of this soon.
@carlos-zamora commented on GitHub (Jun 15, 2020): The latest branch is [cinnamon/settings-ui-v2](https://github.com/microsoft/terminal/tree/cinnamon/settings-ui-v2). We implemented the Settings UI as a separate app that can be found under src/TerminalSettings. We're still working on organizing a plan/spec for the Settings UI as a whole, so feel free to clean up the Globals and Color Schemes page for now, or poke around. For the record, some of the stuff that we still need to plan out are... - changes to the Profiles page - overall design of the Keybindings page - how to sync the JSON and the Settings UI We have some ideas, but we'll come out with an actual spec for all of this soon.
claunia commented 2026-01-30 22:48:06 +00:00
Author
Owner
Copy Link

@Viniacamp commented on GitHub (Jul 8, 2020):

How I execute the app(Settings page)?

@Viniacamp commented on GitHub (Jul 8, 2020): How I execute the app(Settings page)?
claunia commented 2026-01-30 22:48:07 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 8, 2020):

How I execute the app(Settings page)?

The Settings UI is under active development and is not in Windows Terminal yet.

@carlos-zamora commented on GitHub (Jul 8, 2020): > How I execute the app(Settings page)? The Settings UI is under active development and is not in Windows Terminal yet.
claunia commented 2026-01-30 22:48:07 +00:00
Author
Owner
Copy Link

@Viniacamp commented on GitHub (Jul 8, 2020):

Yes, I know this, but isn't it possible to test the prototype of the configuration page, to see how it can look? because at the beginning of the topic there are images of a prototype.

@Viniacamp commented on GitHub (Jul 8, 2020): Yes, I know this, but isn't it possible to test the prototype of the configuration page, to see how it can look? because at the beginning of the topic there are images of a prototype.
claunia commented 2026-01-30 22:48:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 8, 2020):

I believe those are just UI mockups made in Figma, not an actual prototype that can be played with quite yet.

@zadjii-msft commented on GitHub (Jul 8, 2020): I believe those are just UI mockups made in Figma, not an actual prototype that can be played with quite yet.
claunia commented 2026-01-30 22:48:07 +00:00
Author
Owner
Copy Link

@Viniacamp commented on GitHub (Jul 8, 2020):

I downloaded a zip with with this supposed prototype, and now I don’t know how to run it
Anotação 2020-07-08 164816

@Viniacamp commented on GitHub (Jul 8, 2020): I downloaded a zip with with this supposed prototype, and now I don’t know how to run it ![Anotação 2020-07-08 164816](https://user-images.githubusercontent.com/68025681/86963426-e572ee80-c13a-11ea-9361-0ea9dbde2531.jpg)
claunia commented 2026-01-30 22:48:08 +00:00
Author
Owner
Copy Link

@Viniacamp commented on GitHub (Jul 8, 2020):

I believe those are just UI mockups made in Figma, not an actual prototype that can be played with quite yet.

yes, it may be, but the image appears to be so real ...

@Viniacamp commented on GitHub (Jul 8, 2020): > I believe those are just UI mockups made in Figma, not an actual prototype that can be played with quite yet. yes, it may be, but the image appears to be so real ...
claunia commented 2026-01-30 22:48:08 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jul 9, 2020):

@Viniacamp You need to compile the application yourself. There's a TerminalSettings.sln file in the src\TerminalSettings directory which you can open in in Visual Studio and then build and run. But if you don't know what you're doing you may struggle to get it working - I know I had to mess with the project files to adjust the package paths for my system. Also note that there isn't that much to see yet - it's just a few mockups of some of the screens, and that doesn't include any of the images posted at top of the issue.

@j4james commented on GitHub (Jul 9, 2020): @Viniacamp You need to compile the application yourself. There's a `TerminalSettings.sln` file in the `src\TerminalSettings` directory which you can open in in Visual Studio and then build and run. But if you don't know what you're doing you may struggle to get it working - I know I had to mess with the project files to adjust the package paths for my system. Also note that there isn't that much to see yet - it's just a few mockups of some of the screens, and that doesn't include any of the images posted at top of the issue.
claunia commented 2026-01-30 22:48:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 17, 2020):

The "unsaved changes" thing obstructs the settings at the bottom of the page, and they can't be scrolled up.

@DHowett commented on GitHub (Oct 17, 2020): The "unsaved changes" thing obstructs the settings at the bottom of the page, and they can't be scrolled up.
claunia commented 2026-01-30 22:48:08 +00:00
Author
Owner
Copy Link

@SFM61319 commented on GitHub (Oct 18, 2020):

Will there be an autosave feature? like as soon as you check a checkbutton, toggle a toggleswitch, or just change any setting, will they be saved? (event-based save feature)

@SFM61319 commented on GitHub (Oct 18, 2020): Will there be an autosave feature? like as soon as you check a checkbutton, toggle a toggleswitch, or just change any setting, will they be saved? (event-based save feature)
claunia commented 2026-01-30 22:48:09 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 18, 2020):

@SFM61319 because all open instances of Terminal automatically update when the settings file changes, we decided that it would be too dangerous and disruptive to save on every state change. Configuring a single profile would turn every terminal window into an absolute kaleidoscope of font sizes and colors while you were editing.

@DHowett commented on GitHub (Oct 18, 2020): @SFM61319 because all open instances of Terminal automatically update when the settings file changes, we decided that it would be too dangerous and disruptive to save on every state change. Configuring a single profile would turn every terminal window into an absolute kaleidoscope of font sizes and colors while you were editing.
claunia commented 2026-01-30 22:48:09 +00:00
Author
Owner
Copy Link

@SFM61319 commented on GitHub (Oct 18, 2020):

@DHowett wait I have an idea what about a setting (in settings) to enable autosave?

@SFM61319 commented on GitHub (Oct 18, 2020): @DHowett wait I have an idea what about a setting (in settings) to enable autosave?
claunia commented 2026-01-30 22:48:09 +00:00
Author
Owner
Copy Link

@SFM61319 commented on GitHub (Oct 18, 2020):

And will Ctrl + S save the settings so that one doesn't have to click the save button (if autosave isn't a feature)? (Keybindings make stuff easier to use)

@SFM61319 commented on GitHub (Oct 18, 2020): And will `Ctrl + S` save the settings so that one doesn't have to click the save button (if autosave isn't a feature)? (Keybindings make stuff easier to use)
claunia commented 2026-01-30 22:48:09 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Oct 26, 2020):

I have been thinking, is there a plan to include an Import and Export button/option for the ColorScheme?

I know there is the JSON settings page, but it would also be useful to support importing existing colour schemes like iTerm, JSON, or even raw TXT files.

@mdtauk commented on GitHub (Oct 26, 2020): I have been thinking, is there a plan to include an Import and Export button/option for the ColorScheme? I know there is the JSON settings page, but it would also be useful to support importing existing colour schemes like iTerm, JSON, or even raw TXT files.
claunia commented 2026-01-30 22:48:09 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 28, 2020):

@leonmsft you're gonna think I'm crazy, but.. the color schemes page is mixing up all the colors o_O

  1. select campbell

image

  1. keyboard down to campbell powershell

image

  1. keyboard back up to campbell

image

@DHowett commented on GitHub (Oct 28, 2020): @leonmsft you're gonna think I'm crazy, but.. the color schemes page is mixing up all the colors o_O 1. select campbell ![image](https://user-images.githubusercontent.com/189190/97396602-a234bb00-18a4-11eb-9063-3a29a22d2150.png) 2. keyboard down to campbell powershell ![image](https://user-images.githubusercontent.com/189190/97396620-a8c33280-18a4-11eb-9837-a0848cef0588.png) 3. keyboard back up to campbell ![image](https://user-images.githubusercontent.com/189190/97396625-ad87e680-18a4-11eb-80c9-67aa23edb823.png)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Settings Area-UserInterface Issue-Scenario Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2141
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?