starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Settings doesn't open reliably when there's no association for .json files #1968

New Issue
Closed
opened 2026-01-30 22:43:02 +00:00 by claunia · 15 comments
claunia commented 2026-01-30 22:43:02 +00:00
Owner
Copy Link

Originally created by @Mustafa5040 on GitHub (Jun 23, 2019).

When I press the settings on the Windows Terminal, it asks me how I want to open the .json file. So the settings won't open. Please help me

Originally created by @Mustafa5040 on GitHub (Jun 23, 2019). When I press the settings on the Windows Terminal, it asks me how I want to open the .json file. So the settings won't open. Please help me
claunia commented 2026-01-30 22:43:03 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

easy solution, u need a text editor. as simple as that. notepad++ or vs code will be perfect for it. your plain old notepad can do the trick too, but it is easier to edit in smarter text editors as it shows the .json in a formated way.

@Shorotshishir commented on GitHub (Jun 23, 2019): easy solution, u need a text editor. as simple as that. `notepad++` or` vs code` will be perfect for it. your plain old notepad can do the trick too, but it is easier to edit in smarter text editors as it shows the .json in a formated way.
claunia commented 2026-01-30 22:43:04 +00:00
Author
Owner
Copy Link

@hosser commented on GitHub (Jun 23, 2019):

Settings doesn't open for me either, but I don't get any kind of prompt. It just does nothing.

For what it's worth, I have Notepad++ installed.

Never mind, ignore me - I configured Notepad++ as the default file handler for JSON files (I didn't have one set) and now Settings opens that file correctly. So it's a simple filetype association issue.

@hosser commented on GitHub (Jun 23, 2019): Settings doesn't open for me either, but I don't get any kind of prompt. It just does nothing. For what it's worth, I have Notepad++ installed. Never mind, ignore me - I configured Notepad++ as the default file handler for JSON files (I didn't have one set) and now Settings opens that file correctly. So it's a simple filetype association issue.
claunia commented 2026-01-30 22:43:04 +00:00
Author
Owner
Copy Link

@JushBJJ commented on GitHub (Jun 23, 2019):

For settings, customise the terminal by editing the file "profiles.json" in
C:\Users\Your_Username\AppData\Local\Packages\Microsoft.WindowsTerminal_<some random characters>\RoamingState\profiles.json

@JushBJJ commented on GitHub (Jun 23, 2019): For settings, customise the terminal by editing the file "profiles.json" in `C:\Users\Your_Username\AppData\Local\Packages\Microsoft.WindowsTerminal_<some random characters>\RoamingState\profiles.json`
claunia commented 2026-01-30 22:43:04 +00:00
Author
Owner
Copy Link

@drk-mtr commented on GitHub (Jun 23, 2019):

I was having the same issue - thanks for providing the solution.

Might be worth adding a prompt the first time someone attempts to use the Settings menu to advise them to check their file associations if it doesn't work? Or maybe as part of the install process if people don't want to clutter the program with these additional checks.

@drk-mtr commented on GitHub (Jun 23, 2019): I was having the same issue - thanks for providing the solution. Might be worth adding a prompt the first time someone attempts to use the `Settings` menu to advise them to check their file associations if it doesn't work? Or maybe as part of the install process if people don't want to clutter the program with these additional checks.
claunia commented 2026-01-30 22:43:04 +00:00
Author
Owner
Copy Link

@hosser commented on GitHub (Jun 23, 2019):

I was having the same issue - thanks for providing the solution.

Might be worth adding a prompt the first time someone attempts to use the Settings menu to advise them to check their file associations if it doesn't work? Or maybe as part of the install process if people don't want to clutter the program with these additional checks.

Yeah - something needs to be done, as new users will have no idea the terminal is trying to open a .json file. I certainly didn't. So I had no reason to check the file handler for JSON files until I read others descriptions of what happens when they click Settings. Some kind of clue as to what the program is trying to do to enable basic troubleshooting would be nice.

@hosser commented on GitHub (Jun 23, 2019): > I was having the same issue - thanks for providing the solution. > > Might be worth adding a prompt the first time someone attempts to use the `Settings` menu to advise them to check their file associations if it doesn't work? Or maybe as part of the install process if people don't want to clutter the program with these additional checks. Yeah - something needs to be done, as new users will have no idea the terminal is trying to open a .json file. I certainly didn't. So I had no reason to check the file handler for JSON files until I read others descriptions of what happens when they click Settings. Some kind of clue as to what the program is trying to do to enable basic troubleshooting would be nice.
claunia commented 2026-01-30 22:43:04 +00:00
Author
Owner
Copy Link

@JushBJJ commented on GitHub (Jun 23, 2019):

Agreed, I kinda suggest to automatically open notepad to edit profiles.json since its pre-installed in Windows systems and it would be uncommon for a normal user to uninstall it.

@JushBJJ commented on GitHub (Jun 23, 2019): Agreed, I kinda suggest to automatically open notepad to edit `profiles.json` since its pre-installed in Windows systems and it would be uncommon for a normal user to uninstall it.
claunia commented 2026-01-30 22:43:05 +00:00
Author
Owner
Copy Link

@mubeenpatel99 commented on GitHub (Jun 23, 2019):

You can Find the settings manually in the folder:

C:\Users\<YOUR_USERNAME>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState

You can download these Icons and paste them in the same folder as profile.json for a better look:

icons and profile.zip

Snapshot:

Screenshot (42)

@mubeenpatel99 commented on GitHub (Jun 23, 2019): ### You can Find the settings manually in the folder: ```C:\Users\<YOUR_USERNAME>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState``` #### You can download these Icons and paste them in the same folder as profile.json for a better look: [icons and profile.zip](https://github.com/microsoft/terminal/files/3318060/icons.and.profile.zip) ### Snapshot: ![Screenshot (42)](https://user-images.githubusercontent.com/42268754/59979063-4ac37280-9600-11e9-9834-02a10bbb040a.png)
claunia commented 2026-01-30 22:43:05 +00:00
Author
Owner
Copy Link

@drk-mtr commented on GitHub (Jun 23, 2019):

@mubeenpatel99 are you able to share the settings.json that you configured in order to get ubuntu to run as a shell please?

I've tried manually pointing at ubuntu, ubuntu.exe and C:\Users\MyProfileName\AppData\Local\Microsoft\WindowsApps\ubuntu.exe instead of cmd.exe but no luck so far...

Edit: Please ignore - I've reinstalled and found it's "commandline" : "wsl.exe -d Ubuntu",

@drk-mtr commented on GitHub (Jun 23, 2019): @mubeenpatel99 are you able to share the settings.json that you configured in order to get ubuntu to run as a shell please? I've tried manually pointing at `ubuntu`, `ubuntu.exe` and `C:\Users\MyProfileName\AppData\Local\Microsoft\WindowsApps\ubuntu.exe` instead of `cmd.exe` but no luck so far... **Edit:** Please ignore - I've reinstalled and found it's `"commandline" : "wsl.exe -d Ubuntu",`
claunia commented 2026-01-30 22:43:05 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

@drk-mtr please refer to this issue #1449
you will find the correct pattern for the WSL terminal command, for ubuntu it should look like this
commandline parameter : wsl.exe -d ubuntu-linux

@Shorotshishir commented on GitHub (Jun 23, 2019): @drk-mtr please refer to this issue #1449 you will find the correct pattern for the WSL terminal command, for ubuntu it should look like this commandline parameter : `wsl.exe -d ubuntu-linux`
claunia commented 2026-01-30 22:43:05 +00:00
Author
Owner
Copy Link

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

@mubeenpatel99 are you able to share the settings.json that you configured in order to get ubuntu to run as a shell please?

I've tried manually pointing at ubuntu, ubuntu.exe and C:\Users\MyProfileName\AppData\Local\Microsoft\WindowsApps\ubuntu.exe instead of cmd.exe but no luck so far...

Edit: Please ignore - I've reinstalled and found it's "commandline" : "wsl.exe -d Ubuntu",

Yeah great it's working now

@mubeenpatel99 commented on GitHub (Jun 24, 2019): > @mubeenpatel99 are you able to share the settings.json that you configured in order to get ubuntu to run as a shell please? > > I've tried manually pointing at `ubuntu`, `ubuntu.exe` and `C:\Users\MyProfileName\AppData\Local\Microsoft\WindowsApps\ubuntu.exe` instead of `cmd.exe` but no luck so far... > > **Edit:** Please ignore - I've reinstalled and found it's `"commandline" : "wsl.exe -d Ubuntu",` Yeah great it's working now
claunia commented 2026-01-30 22:43:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

Re-titled to make this a little more robust.

@DHowett-MSFT commented on GitHub (Jun 24, 2019): Re-titled to make this a little more robust.
claunia commented 2026-01-30 22:43:05 +00:00
Author
Owner
Copy Link

@levicki commented on GitHub (Jul 2, 2019):

If you change startingDirectory value you must use either forward slashes (/) or escaped backslashes (\\) in the filesystem path or the Terminal will refuse to reload settings due to invalid Json format.

To a front-end developer this might be obvious, but not for regular users.

@levicki commented on GitHub (Jul 2, 2019): If you change `startingDirectory` value you must use either forward slashes (`/`) or escaped backslashes (`\\`) in the filesystem path or the Terminal will refuse to reload settings due to invalid Json format. To a front-end developer this might be obvious, but not for regular users.
claunia commented 2026-01-30 22:43:06 +00:00
Author
Owner
Copy Link

@HAWK-Soft commented on GitHub (Jul 4, 2019):

@mubeenpatel99 are you able to share the settings.json that you configured in order to get ubuntu to run as a shell please?
I've tried manually pointing at ubuntu, ubuntu.exe and C:\Users\MyProfileName\AppData\Local\Microsoft\WindowsApps\ubuntu.exe instead of cmd.exe but no luck so far...
Edit: Please ignore - I've reinstalled and found it's "commandline" : "wsl.exe -d Ubuntu",

Yeah great it's working now

I think these links are useful before complete this config file (profiles.json). Thanks for your help guys! (:

https://docs.microsoft.com/en-gb/windows/wsl/install-win10
https://docs.microsoft.com/en-gb/windows/wsl/about

@HAWK-Soft commented on GitHub (Jul 4, 2019): > > > > @mubeenpatel99 are you able to share the settings.json that you configured in order to get ubuntu to run as a shell please? > > I've tried manually pointing at `ubuntu`, `ubuntu.exe` and `C:\Users\MyProfileName\AppData\Local\Microsoft\WindowsApps\ubuntu.exe` instead of `cmd.exe` but no luck so far... > > **Edit:** Please ignore - I've reinstalled and found it's `"commandline" : "wsl.exe -d Ubuntu",` > > Yeah great it's working now I think these links are useful before complete this config file (profiles.json). Thanks for your help guys! (: [https://docs.microsoft.com/en-gb/windows/wsl/install-win10](url) [https://docs.microsoft.com/en-gb/windows/wsl/about](url)
claunia commented 2026-01-30 22:43:06 +00:00
Author
Owner
Copy Link

@metathinker commented on GitHub (Jul 10, 2019):

I believe https://github.com/microsoft/terminal/pull/1841 fixes this issue (no .json file editor registered prevents profiles.json from opening).

@metathinker commented on GitHub (Jul 10, 2019): I believe https://github.com/microsoft/terminal/pull/1841 fixes this issue (no .json file editor registered prevents profiles.json from opening).
claunia commented 2026-01-30 22:43:06 +00:00
Author
Owner
Copy Link

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

Hey, good catch! Thanks.

@DHowett-MSFT commented on GitHub (Jul 10, 2019): Hey, good catch! Thanks.
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 Help Wanted Issue-Bug Product-Terminal Resolution-Fix-Committed
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#1968
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?