Settings Button #11119

Closed
opened 2026-01-31 02:39:09 +00:00 by claunia · 3 comments
Owner

Originally created by @MMS2005 on GitHub (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

Originally created by @MMS2005 on GitHub (Oct 22, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # 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
claunia added the Resolution-Duplicate label 2026-01-31 02:39:09 +00:00
Author
Owner

@j4james commented on GitHub (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 https://github.com/microsoft/terminal/issues/7975#issuecomment-712880743.

@j4james commented on GitHub (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 https://github.com/microsoft/terminal/issues/7975#issuecomment-712880743.
Author
Owner

@zadjii-msft commented on GitHub (Oct 22, 2020):

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

@zadjii-msft commented on GitHub (Oct 22, 2020): 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
Author
Owner

@ghost commented on GitHub (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 commented on GitHub (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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11119