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

Settings does not open #1861

New Issue
Closed
opened 2026-01-30 22:40:17 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:40:17 +00:00
Owner
Copy Link

Originally created by @benbrackenbury on GitHub (Jun 22, 2019).

Environment

Windows build number: 18922
Windows Terminal version (if applicable): 0.2.1715.0

Any other software?

Steps to reproduce

Clicking on the Settings item in the menu, or pressing Ctrl+,

Expected behavior

Settings.json should open

Actual behavior

Settings.json does not open

Originally created by @benbrackenbury on GitHub (Jun 22, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 18922 Windows Terminal version (if applicable): 0.2.1715.0 Any other software? ``` # Steps to reproduce Clicking on the Settings item in the menu, or pressing Ctrl+, # Expected behavior Settings.json should open # Actual behavior Settings.json does not open
claunia added the Area-SettingsNeeds-Tag-FixResolution-DuplicateProduct-Terminal labels 2026-01-30 22:40:17 +00:00
claunia commented 2026-01-30 22:40:18 +00:00
Author
Owner
Copy Link

@cherichy commented on GitHub (Jun 22, 2019):

Same with you, but I can open it if I click the Setting, but not for Ctrl+,

@cherichy commented on GitHub (Jun 22, 2019): Same with you, but I can open it if I click the Setting, but not for Ctrl+,
claunia commented 2026-01-30 22:40:18 +00:00
Author
Owner
Copy Link

@benbrackenbury commented on GitHub (Jun 22, 2019):

Never mind, I found a solution. Turn out I didn't have any application set as the default for opening json files. After I set VS Code as the default, it worked as expected

@benbrackenbury commented on GitHub (Jun 22, 2019): Never mind, I found a solution. Turn out I didn't have any application set as the default for opening json files. After I set VS Code as the default, it worked as expected
claunia commented 2026-01-30 22:40:19 +00:00
Author
Owner
Copy Link

@doterik commented on GitHub (Jun 22, 2019):

Experienced exactly the same problem as @benbrackenbury.
After the same solution, it worked as expected.

@doterik commented on GitHub (Jun 22, 2019): Experienced exactly the same problem as @benbrackenbury. After the same solution, it worked as expected.
claunia commented 2026-01-30 22:40:19 +00:00
Author
Owner
Copy Link

@laolusrael commented on GitHub (Jun 22, 2019):

I had the same experience

@laolusrael commented on GitHub (Jun 22, 2019): I had the same experience
claunia commented 2026-01-30 22:40:19 +00:00
Author
Owner
Copy Link

@adiviness commented on GitHub (Jun 24, 2019):

#1460

@adiviness commented on GitHub (Jun 24, 2019): #1460
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 Needs-Tag-Fix Product-Terminal Resolution-Duplicate
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#1861
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?