Bug Report: Settings Do Not Open #2847

Closed
opened 2026-01-30 23:06:59 +00:00 by claunia · 4 comments
Owner

Originally created by @lnorton89 on GitHub (Jul 19, 2019).

Environment

Windows build number: 10.0.18362.239
Windows Terminal version: Latest

Steps to reproduce

Open Windows Terminal and try to open the settings via the arrow button.

Expected behavior

A settings dialog opens.

Actual behavior

Nothing.

Originally created by @lnorton89 on GitHub (Jul 19, 2019). # Environment ```none Windows build number: 10.0.18362.239 Windows Terminal version: Latest ``` # Steps to reproduce Open Windows Terminal and try to open the settings via the arrow button. # Expected behavior A settings dialog opens. # Actual behavior Nothing.
claunia added the Resolution-Duplicate label 2026-01-30 23:06:59 +00:00
Author
Owner

@alefnull commented on GitHub (Jul 19, 2019):

currently the settings are stored in and edited via a JSON file, so you'll need to associate a text editor with JSON files in your system settings. after that, clicking the settings button will open the settings JSON file for you to edit as you wish.

@alefnull commented on GitHub (Jul 19, 2019): currently the settings are stored in and edited via a JSON file, so you'll need to associate a text editor with JSON files in your system settings. after that, clicking the settings button will open the settings JSON file for you to edit as you wish.
Author
Owner

@kyleskrinak commented on GitHub (Jul 19, 2019):

I have confirmed that my system has mapped *.json to vim, yet control-comma or choosing “Settings” from the tabbed menu fails to load the settings file. Or, as the OP says; “nothing” happens.

@kyleskrinak commented on GitHub (Jul 19, 2019): I have confirmed that my system has mapped *.json to vim, yet control-comma or choosing “Settings” from the tabbed menu fails to load the settings file. Or, as the OP says; “nothing” happens.
Author
Owner

@DHowett-MSFT commented on GitHub (Jul 20, 2019):

Alas, this is a silly bug. #1789
It's been fixed, and that fix is just waiting for another release.

@DHowett-MSFT commented on GitHub (Jul 20, 2019): Alas, this is a silly bug. #1789 It's been fixed, and that fix is just waiting for another release.
Author
Owner

@DHowett-MSFT commented on GitHub (Jul 20, 2019):

The core of the issue is that gvim registers itself for the "edit" verb but we were using the "open" verb.
The fix for 1789 also added a fallback to Notepad just in case nothing was able to open it.

@DHowett-MSFT commented on GitHub (Jul 20, 2019): The core of the issue is that gvim registers itself for the "edit" verb but we were using the "open" verb. The fix for 1789 also added a fallback to Notepad just in case nothing was able to open it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2847