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

Trying to access settings pulls up the 'Open with' popup dialog #12949

New Issue
Closed
opened 2026-01-31 03:29:44 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:29:44 +00:00
Owner
Copy Link

Originally created by @rectified95 on GitHub (Mar 10, 2021).

Environment

Windows build number: Win32NT             10.0.21322.0 Microsoft Windows NT 10.0.21322.0
Windows Terminal version (if applicable): 1.6.10571.0
Any other software?

Steps to reproduce

  1. Press "Ctrl+,' in order to open terminal settings.

Expected behavior

Can access terminal settings - would expect to be able to change font size/color there.

Actual behavior

A popup dialog comes up prompting me to choose the app with which to open some file - 'how do you want to open this file?'

Originally created by @rectified95 on GitHub (Mar 10, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Win32NT 10.0.21322.0 Microsoft Windows NT 10.0.21322.0 Windows Terminal version (if applicable): 1.6.10571.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Press "Ctrl+,' in order to open terminal settings. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Can access terminal settings - would expect to be able to change font size/color there. # Actual behavior <!-- What's actually happening? --> A popup dialog comes up prompting me to choose the app with which to open some file - 'how do you want to open this file?'
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 03:29:44 +00:00
claunia commented 2026-01-31 03:29:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 10, 2021):

You didn't mention a version for the Terminal, but I'm presuming you're running <1.7.*. EDIT: updated while I was typing

That's exactly by design - the settings for the Terminal are in a json file - when you click on "Settings", it'll try and open the settings.json file in whatever your default .json editor is. If there isn't one configured, then you'll get that dialog.

@zadjii-msft commented on GitHub (Mar 10, 2021): ~~You didn't mention a version for the Terminal, but I'm presuming you're running <1.7.*.~~ EDIT: updated while I was typing That's exactly by design - the settings for the Terminal are in a json file - when you click on "Settings", it'll try and open the `settings.json` file in whatever your default `.json` editor is. If there isn't one configured, then you'll get that dialog.
claunia commented 2026-01-31 03:29:46 +00:00
Author
Owner
Copy Link

@rectified95 commented on GitHub (Mar 10, 2021):

I'd say it should default to at least Notepad, and/or inform that settings are stored in a JSON file.

@rectified95 commented on GitHub (Mar 10, 2021): I'd say it should default to at least Notepad, and/or inform that settings are stored in a JSON file.
claunia commented 2026-01-31 03:29:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 10, 2021):

Unfortunately, when we ask the OS to open the "default json editor", I'm not sure there's a way for us to know that it couldn't find an app and let us fall back to notepad gracefully.

In 1.7 (in preview now), the terminal actually defaults to the new Settings UI, so this won't really be an issue in one release ☺️.

@zadjii-msft commented on GitHub (Mar 10, 2021): Unfortunately, when we ask the OS to open the "default json editor", I'm not sure there's a way for us to know that it couldn't find an app and let us fall back to notepad gracefully. In 1.7 (in preview _now_), the terminal actually defaults to the new Settings UI, so this won't really be an issue in one release ☺️.
claunia commented 2026-01-31 03:29:46 +00:00
Author
Owner
Copy Link

@rectified95 commented on GitHub (Mar 10, 2021):

Thanks for getting back to me.

the terminal actually defaults to the new Settings UI

do you mean that the 'default apps' page in the Windows Settings app will be opened when the terminal can't find a default JSON editor?

@rectified95 commented on GitHub (Mar 10, 2021): Thanks for getting back to me. > the terminal actually defaults to the new Settings UI do you mean that the 'default apps' page in the Windows Settings app will be opened when the terminal can't find a default JSON editor?
claunia commented 2026-01-31 03:29:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 10, 2021):

Thanks for getting back to me.

the terminal actually defaults to the new Settings UI

do you mean that the 'default apps' page in the Windows Settings app will be opened when the terminal can't find a default JSON editor?

Nope! This is what you'll get:

image

@DHowett commented on GitHub (Mar 10, 2021): > Thanks for getting back to me. > > > the terminal actually defaults to the new Settings UI > > do you mean that the 'default apps' page in the Windows Settings app will be opened when the terminal can't find a default JSON editor? Nope! This is what you'll get: ![image](https://user-images.githubusercontent.com/189190/110712178-6ac90a00-81c6-11eb-929c-d84755e9c6b9.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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#12949
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?