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

Settings UI Is Not Visible #9134

Closed
opticyclic opened this issue Feb 12, 2021 · 3 comments
Closed

Settings UI Is Not Visible #9134

opticyclic opened this issue Feb 12, 2021 · 3 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@opticyclic
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.19042.746]
Windows Terminal version: 1.6.10412.0

Steps to reproduce

Start Windows Terminal Preview
Press Ctrl-,

Expected behavior

The new Settings UI appears.

Actual behavior

The settings json file appears

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 12, 2021
@WSLUser
Copy link
Contributor

WSLUser commented Feb 12, 2021

You need to add a keybinding in settings.json in order to open the Settings UI. The release notes (and docs) have the line entry you need to bind it. Because it's in Preview still, you can't use it by default.

@DHowett DHowett closed this as completed Feb 12, 2021
@DHowett
Copy link
Member

DHowett commented Feb 12, 2021

Yup!

@opticyclic
Copy link
Author

FYI: It would have been nicer if you had copied the relevant part of the answer here (a la stackoverflow) or linked to the "release notes (and docs)".

TLDR:

Until it's ready for prime time, it's hidden behind a NON-DEFAULT key binding. (#8048)
To bind the settings UI to Ctrl+Shift+,, add the following to your keybindings/actions.

{ "command": { "action": "openSettings", "target": "settingsUI" }, "keys": "ctrl+shift+," },

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

3 participants