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

[PR #5915] [MERGED] Add Mini-Spec for openSettings #26534

New Issue
Open
opened 2026-01-31 09:16:40 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:16:40 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/5915
Author: @carlos-zamora
Created: 5/14/2020
Status: ✅ Merged
Merged: 6/11/2020
Merged by: @carlos-zamora

Base: master ← Head: dev/cazamor/spec/settings-kbd

📝 Commits (5)

  • a4e23b5 Add Mini-Spec for openSettings
  • 85a7438 PR Feedback
  • 667dd27 add conclusion and mention 'allSettingsFiles'
  • d93df96 restructure spec for better flow
  • d53f787 add a future consideration

📊 Changes

1 file changed (+135 additions, -0 deletions)

View changed files

➕ doc/specs/#2557 - Settings Keybinding.md (+135 -0)

📄 Description

Summary of the Pull Request

As I was looking at #2557, I realized that the addition of a Settings UI could make things a little weird. I decided to add a mini spec to discuss what to do.

The implementation of this feature shouldn't be too difficult. I more just want to openly discuss what we think the right approach should be.

References

#2557 - open defaults keybinding

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/5915 **Author:** [@carlos-zamora](https://github.com/carlos-zamora) **Created:** 5/14/2020 **Status:** ✅ Merged **Merged:** 6/11/2020 **Merged by:** [@carlos-zamora](https://github.com/carlos-zamora) **Base:** `master` ← **Head:** `dev/cazamor/spec/settings-kbd` --- ### 📝 Commits (5) - [`a4e23b5`](https://github.com/microsoft/terminal/commit/a4e23b530f6998d5933bd8085114f7095947a2d0) Add Mini-Spec for openSettings - [`85a7438`](https://github.com/microsoft/terminal/commit/85a74386e9ac826e3eda254033f29f526e6a411e) PR Feedback - [`667dd27`](https://github.com/microsoft/terminal/commit/667dd27574cefa7aeb1612f099fbc945dd487d36) add conclusion and mention 'allSettingsFiles' - [`d93df96`](https://github.com/microsoft/terminal/commit/d93df967e1b11e27ad997f9896e23058fe7a0dde) restructure spec for better flow - [`d53f787`](https://github.com/microsoft/terminal/commit/d53f78729cf870bb4a6bdb0558ec3d21423a657e) add a future consideration ### 📊 Changes **1 file changed** (+135 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `doc/specs/#2557 - Settings Keybinding.md` (+135 -0) </details> ### 📄 Description ## Summary of the Pull Request As I was looking at #2557, I realized that the addition of a Settings UI could make things a little weird. I decided to add a mini spec to discuss what to do. The implementation of this feature shouldn't be too difficult. I more just want to openly discuss what we think the right approach should be. ## References #2557 - open defaults keybinding --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:16:40 +00:00
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 pull-request
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#26534
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?