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

I couldn't run the Setting window #11898

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

Originally created by @seohyeonShin on GitHub (Dec 28, 2020).

Environment

windows10, install visual studio 2013 prof. install VSCode, WSL 2.

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

  1. windows10, install visual studio 2013 prof. install VSCode, WSL 2.
  2. run windows terminal with ubuntu(actually, I think that is not matter)
  3. right click and select the setting on windows terminal upper bar.
  4. and than Visual studio2013 is executed without any file or any information.

Expected behavior

just open setting text file on VS CODE or other text edit program.

image

Actual behavior

image
image

Visual Studio runs if i click the setting, without any informataion.
I use visual studio 2013 for work.

Originally created by @seohyeonShin on GitHub (Dec 28, 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 windows10, install visual studio 2013 prof. install VSCode, WSL 2. ```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. --> 0. windows10, install visual studio 2013 prof. install VSCode, WSL 2. 1. run windows terminal with ubuntu(actually, I think that is not matter) 2. right click and select the setting on windows terminal upper bar. 3. and than Visual studio2013 is executed without any file or any information. # Expected behavior just open setting text file on VS CODE or other text edit program. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> ![image](https://user-images.githubusercontent.com/17170771/103199274-d9b7f600-492d-11eb-8ef9-39280488b852.png) # Actual behavior ![image](https://user-images.githubusercontent.com/17170771/103199199-a8d7c100-492d-11eb-98e5-de4a9f283ee2.png) ![image](https://user-images.githubusercontent.com/17170771/103199230-b8570a00-492d-11eb-9c09-7ca0400828d6.png) <!-- What's actually happening? --> Visual Studio runs if i click the setting, without any informataion. I use visual studio 2013 for work.
claunia added the Issue-QuestionArea-SettingsNeeds-Tag-FixProduct-Terminal labels 2026-01-31 03:00:30 +00:00
claunia commented 2026-01-31 03:00:31 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Dec 28, 2020):

If you double-click the settings.json file in File Explorer, does Visual Studio 2013 likewise start without opening the file? If it does, I think the fault is not in Windows Terminal.

@KalleOlaviNiemitalo commented on GitHub (Dec 28, 2020): If you double-click the `settings.json` file in File Explorer, does Visual Studio 2013 likewise start without opening the file? If it does, I think the fault is not in Windows Terminal.
claunia commented 2026-01-31 03:00:31 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 28, 2020):

@seohyeonShin Windows Terminal opens your settings.json file with the default text editor for json files. Sounds like you have Visual Studio 2013 set as your default there. Try this:

  1. go to the Settings app for Windows
  2. select Apps > Default apps > Choose default apps by file type
  3. scroll down to .json and set the default app to VS Code

Relevant Settings App page

Let me know if this works for you 😊

@carlos-zamora commented on GitHub (Dec 28, 2020): @seohyeonShin Windows Terminal opens your `settings.json` file with the default text editor for json files. Sounds like you have Visual Studio 2013 set as your default there. Try this: 1. go to the Settings app for Windows 2. select Apps > Default apps > Choose default apps by file type 3. scroll down to .json and set the default app to VS Code ![Relevant Settings App page](https://user-images.githubusercontent.com/11050425/103225370-5ecfea80-48ef-11eb-9442-17e80a22d86b.png) Let me know if this works for you 😊
claunia commented 2026-01-31 03:00:31 +00:00
Author
Owner
Copy Link

@seohyeonShin commented on GitHub (Dec 29, 2020):

image
I couldn't choice other tool,,,
I can't understand that why I can choice only visual studio and only find in MS store.

@seohyeonShin commented on GitHub (Dec 29, 2020): ![image](https://user-images.githubusercontent.com/17170771/103251026-44af0e80-49ba-11eb-97c6-d2dc8c796344.png) I couldn't choice other tool,,, I can't understand that why I can choice only visual studio and only find in MS store.
claunia commented 2026-01-31 03:00:31 +00:00
Author
Owner
Copy Link

@Chips1234 commented on GitHub (Dec 30, 2020):

@seohyeonShin You have VSCode installed, yes?

@Chips1234 commented on GitHub (Dec 30, 2020): @seohyeonShin You have VSCode installed, yes?
claunia commented 2026-01-31 03:00:31 +00:00
Author
Owner
Copy Link

@seohyeonShin commented on GitHub (Dec 31, 2020):

wow,, Thanks! I never expected it to be a problem.
I was able to fix it by referring to your advice.

@seohyeonShin commented on GitHub (Dec 31, 2020): wow,, Thanks! I never expected it to be a problem. I was able to fix it by referring to your advice.
claunia commented 2026-01-31 03:00:32 +00:00
Author
Owner
Copy Link

@Chips1234 commented on GitHub (Dec 31, 2020):

You’re welcome

@Chips1234 commented on GitHub (Dec 31, 2020): You’re welcome
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 Issue-Question Needs-Tag-Fix Product-Terminal
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#11898
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?