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

Choose your own editor for Settings #5016

New Issue
Closed
opened 2026-01-31 00:02:57 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:02:57 +00:00
Owner
Copy Link

Originally created by @AndrewR66 on GitHub (Nov 15, 2019).

When I pick Settings in the dropdown menu, profile.json opens in Visual Studio. This is slow. I would like to open it in a smaller/faster editor. I suppose it opens in VS due to my windows file extension settings for .json files. I don't wan't to change this setting, but I would like a seperate setting where I can choose my editor.

Proposed technical implementation details (optional)

With the new feature:

  1. I will somehow pick editor for editing settings.
  2. When I choose to edit settings, profile.json opens in the editor from 1)
Originally created by @AndrewR66 on GitHub (Nov 15, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> When I pick Settings in the dropdown menu, profile.json opens in Visual Studio. This is slow. I would like to open it in a smaller/faster editor. I suppose it opens in VS due to my windows file extension settings for .json files. I don't wan't to change this setting, but I would like a seperate setting where I can choose my editor. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> With the new feature: 1) I will somehow pick editor for editing settings. 2) When I choose to edit settings, profile.json opens in the editor from 1)
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 00:02:57 +00:00
claunia commented 2026-01-31 00:02:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 18, 2019):

Hey @AndrewR66, thanks for the request! On the balance, this seems like a huge amount of work (providing an in-terminal file association UI) for a pretty narrow use case. If you don't mind, though, why are you averse to changing your default JSON association? VS is going to be huge and take forever to load regardless of which JSON file you're opening, so it might be advantageous to just change the association everywhere.

@DHowett-MSFT commented on GitHub (Nov 18, 2019): Hey @AndrewR66, thanks for the request! On the balance, this seems like a _huge_ amount of work (providing an in-terminal file association UI) for a pretty narrow use case. If you don't mind, though, why are you averse to changing your default JSON association? VS is going to be huge and take forever to load regardless of which JSON file you're opening, so it might be advantageous to just change the association everywhere.
claunia commented 2026-01-31 00:02:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 22, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 22, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 00:02:58 +00:00
Author
Owner
Copy Link

@AndrewR66 commented on GitHub (Nov 27, 2019):

Thank you for responding, I think I'll change my JSON association after all, like you suggest.

@AndrewR66 commented on GitHub (Nov 27, 2019): Thank you for responding, I think I'll change my JSON association after all, like you suggest.
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-Feature Needs-Attention Needs-Tag-Fix Needs-Triage
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#5016
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?