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 Button #8004

Closed
MMS2005 opened this issue Oct 22, 2020 · 3 comments
Closed

Settings Button #8004

MMS2005 opened this issue Oct 22, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@MMS2005
Copy link

MMS2005 commented Oct 22, 2020

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

HI There, I Was Expecting the Settings Button to Open Some Sort of Settings Stuff, But It Did not Do Anything.

Actual behavior

There's no Response From the Terminal

@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 Oct 22, 2020
@j4james
Copy link
Collaborator

j4james commented Oct 22, 2020

The Settings menu just opens the settings.json file in whatever application you've got configured as your default .json editor. If it's not doing anything, that probably means you haven't got an application set as the default editor. For more info see issue #7975 (comment).

@zadjii-msft
Copy link
Member

The settings button will open the settings file (settings.json) in whatever your default editor for json files is configured to be. If there's not one already set, the OS will take a little while before displaying a "what application would you like to open this file in?" dialog.

/dup #1564
/dup #442

@ghost
Copy link

ghost commented Oct 22, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 22, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Oct 22, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants