Add comments and settings to settings.json for discoverability #7227

Closed
opened 2026-01-31 00:58:24 +00:00 by claunia · 1 comment
Owner

Originally created by @cinnamon-msft on GitHub (Mar 30, 2020).

Originally assigned to: @carlos-zamora on GitHub.

Description of the new feature/enhancement

We should add comments above each major section with the link to our documentation.

Additionally, we should add the following settings to settings.json so people can find them easily:

Settings

  • "copyOnSelect": false

Key bindings

  • { "command": "find", "keys": "ctrl+shift+f" }
    This would also be bound in defaults.json, but we can explain "unbound"/null in a comment above it.
  • { "command": {"action": "splitPane", "split": "auto", "splitMode": "duplicate"}, "keys": "alt+shift+d" }
    This is a common panes use case and it also demonstrates the fact that we have panes and shows how the key bindings are formatted.

Proposed technical implementation details (optional)

Originally created by @cinnamon-msft on GitHub (Mar 30, 2020). Originally assigned to: @carlos-zamora on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement We should add comments above each major section with the link to our documentation. Additionally, we should add the following settings to settings.json so people can find them easily: ## Settings - `"copyOnSelect": false` ## Key bindings - `{ "command": "find", "keys": "ctrl+shift+f" }` This would also be bound in defaults.json, but we can explain `"unbound"/null` in a comment above it. - `{ "command": {"action": "splitPane", "split": "auto", "splitMode": "duplicate"}, "keys": "alt+shift+d" }` This is a common panes use case and it also demonstrates the fact that we have panes and shows how the key bindings are formatted. <!-- 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. -->
Author
Owner

@ghost commented on GitHub (Apr 22, 2020):

:tada:This issue was addressed in #5217, which has now been successfully released as Windows Terminal Preview v0.11.1121.0.🎉

Handy links:

@ghost commented on GitHub (Apr 22, 2020): :tada:This issue was addressed in #5217, which has now been successfully released as `Windows Terminal Preview v0.11.1121.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.11.1121.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7227