starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Open settings in default code editor #8865

New Issue
Closed
opened 2026-01-31 01:40:00 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 01:40:00 +00:00
Owner
Copy Link

Originally created by @LinqLover on GitHub (Jun 6, 2020).

Description of the new feature/enhancement

Instead of using notepad, open the settings.json file in the default code editor. This could be inside the terminal: nano, vim, or whatever, or directly in Windows: VS Code, Notepad++ or whatever.

Proposed technical implementation details (optional)

Probably a new entry in the settings.json would be required to specify the path to the default editor.

Originally created by @LinqLover on GitHub (Jun 6, 2020). # Description of the new feature/enhancement Instead of using notepad, open the `settings.json` file in the default code editor. This could be inside the terminal: nano, vim, or whatever, or directly in Windows: VS Code, Notepad++ or whatever. # Proposed technical implementation details (optional) Probably a new entry in the settings.json would be required to specify the path to the default editor.
claunia added the Issue-FeatureNeeds-Tag-FixResolution-Won't-Fix labels 2026-01-31 01:40:00 +00:00
claunia commented 2026-01-31 01:40:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 6, 2020):

Terminal always opens in your default JSON editor. If and ONLY if that association isn’t set does it open in notepad.

I’d suggest checking your file type association settings.

@DHowett commented on GitHub (Jun 6, 2020): Terminal _always_ opens in your default JSON editor. If and ONLY if that association isn’t set does it open in notepad. I’d suggest checking your file type association settings.
claunia commented 2026-01-31 01:40:01 +00:00
Author
Owner
Copy Link

@LinqLover commented on GitHub (Jun 7, 2020):

I see that WT usees the default associated program at the moment, but I could imagine it would be nice if the configuration file would be opened directly in the terminal, no matter what your default JSON editor is. When I open a JSON file in Windows Explorer, notepad is great, but if I'm in a terminal context, I would like to stay there and not be redirected into another program.

@LinqLover commented on GitHub (Jun 7, 2020): I see that WT usees the default associated program at the moment, but I could imagine it would be nice if the configuration file would be opened directly in the terminal, no matter what your default JSON editor is. When I open a JSON file in Windows Explorer, notepad is great, but if I'm in a terminal context, I would like to stay there and not be redirected into another program.
claunia commented 2026-01-31 01:40:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 7, 2020):

But terminal isn't and doesn't ship with a text editor...

Owing to that, you'll probably want #1564 for "edit settings inside the terminal."

@DHowett commented on GitHub (Jun 7, 2020): But terminal isn't and doesn't ship with a text editor... Owing to that, you'll probably want #1564 for "edit settings inside the terminal."
claunia commented 2026-01-31 01:40:02 +00:00
Author
Owner
Copy Link

@LinqLover commented on GitHub (Jun 7, 2020):

Ah yes, this is what I was searching for. /dup #1564, thank you.

@LinqLover commented on GitHub (Jun 7, 2020): Ah yes, this is what I was searching for. /dup #1564, thank you.
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-Tag-Fix Resolution-Won't-Fix
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#8865
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?