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

Cant write brackets [] and a few other symbols in the new windows terminal in any of the shells #14707

New Issue
Closed
opened 2026-01-31 04:17:24 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 04:17:24 +00:00
Owner
Copy Link

Originally created by @leet0rz on GitHub (Jul 27, 2021).

Originally assigned to: @zadjii-msft on GitHub.

Windows Terminal version (or Windows build number)

Microsoft Windows [Version 10.0.19043.1110]

Other Software

Nothing

Steps to reproduce

Just type

Expected Behavior

To be able to type brackets

Actual Behavior

Not typing brackets

Originally created by @leet0rz on GitHub (Jul 27, 2021). Originally assigned to: @zadjii-msft on GitHub. ### Windows Terminal version (or Windows build number) Microsoft Windows [Version 10.0.19043.1110] ### Other Software Nothing ### Steps to reproduce Just type ### Expected Behavior To be able to type brackets ### Actual Behavior Not typing brackets
claunia added the Resolution-Duplicate label 2026-01-31 04:17:24 +00:00
claunia commented 2026-01-31 04:17:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 27, 2021):

What keyboard layout are you using? What version of the Terminal?

@zadjii-msft commented on GitHub (Jul 27, 2021): What keyboard layout are you using? What version of the Terminal?
claunia commented 2026-01-31 04:17:26 +00:00
Author
Owner
Copy Link

@leet0rz commented on GitHub (Jul 29, 2021):

Norwegian.
Version: 1.9.1942.0

I am trying to press ctrl + alt + 8 or 9 which are the bracket keys for me.

@leet0rz commented on GitHub (Jul 29, 2021): Norwegian. Version: 1.9.1942.0 I am trying to press ctrl + alt + 8 or 9 which are the bracket keys for me.
claunia commented 2026-01-31 04:17:26 +00:00
Author
Owner
Copy Link

@zakius commented on GitHub (Jul 30, 2021):

these default to "switch to tab" with respective numbers, you'll need (at least for now) to add { "command": null, "keys": ctrl+alt+8" } and { "command": null, "keys": ctrl+alt+9" } to your settings

when talking about defaults key bindings the moveFocus actions are poorly bound making it impossible to pass alt+cursors to apps and hopefully that can be fixed

out of curiosity: is that AltGr actually or you have to hold both these modifiers at the same time? that feels unusual

@zakius commented on GitHub (Jul 30, 2021): these default to "switch to tab" with respective numbers, you'll need (at least for now) to add `{ "command": null, "keys": ctrl+alt+8" }` and `{ "command": null, "keys": ctrl+alt+9" }` to your settings when talking about defaults key bindings the `moveFocus` actions are poorly bound making it impossible to pass `alt+cursors` to apps and hopefully that can be fixed out of curiosity: is that `AltGr` actually or you have to hold both these modifiers at the same time? that feels unusual
claunia commented 2026-01-31 04:17:26 +00:00
Author
Owner
Copy Link

@leet0rz commented on GitHub (Jul 30, 2021):

The AltGr works but not ctrl + alt + 8 or 9. That is how most of
Scandinavia with our keyboard layout write those brackets. You should
probably consider changing it to not being ctrl + alt, that is how we type
most symbols.

@leet0rz commented on GitHub (Jul 30, 2021): The AltGr works but not ctrl + alt + 8 or 9. That is how most of Scandinavia with our keyboard layout write those brackets. You should probably consider changing it to not being ctrl + alt, that is how we type most symbols.
claunia commented 2026-01-31 04:17:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2021):

You know, we have a dupe for this somewhere in the history.

We definitely goofed when we bound ctrl+alt keybindings in the first place. Unfortunately, the Terminal's shipped far to many releases with those keys bound by default, and we can't go removing them from the defaults without also blowing them away from anyone who might currently be using them 😕. Alas. We certainly won't be shipping any more on ctrl+alt in the future.

You can remove the keybindings with:

        { "command": "unbound", "keys": "ctrl+alt+1" },
        { "command": "unbound", "keys": "ctrl+alt+2" },
        { "command": "unbound", "keys": "ctrl+alt+3" },
        { "command": "unbound", "keys": "ctrl+alt+4" },
        { "command": "unbound", "keys": "ctrl+alt+5" },
        { "command": "unbound", "keys": "ctrl+alt+6" },
        { "command": "unbound", "keys": "ctrl+alt+7" },
        { "command": "unbound", "keys": "ctrl+alt+8" },
        { "command": "unbound", "keys": "ctrl+alt+9" }
@zadjii-msft commented on GitHub (Aug 5, 2021): You know, we have a dupe for this somewhere in the history. * It's not #5525 * It's kinda the same thing as #9909 * Ah, /dup #7177 is the one I was thinking of We definitely goofed when we bound <kbd>ctrl+alt</kbd> keybindings in the first place. Unfortunately, the Terminal's shipped far to many releases with those keys bound by default, and we can't go removing them from the defaults without also blowing them away from anyone who might currently be using them 😕. Alas. We certainly won't be shipping any more on <kbd>ctrl+alt</kbd> in the future. You can remove the keybindings with: ```json { "command": "unbound", "keys": "ctrl+alt+1" }, { "command": "unbound", "keys": "ctrl+alt+2" }, { "command": "unbound", "keys": "ctrl+alt+3" }, { "command": "unbound", "keys": "ctrl+alt+4" }, { "command": "unbound", "keys": "ctrl+alt+5" }, { "command": "unbound", "keys": "ctrl+alt+6" }, { "command": "unbound", "keys": "ctrl+alt+7" }, { "command": "unbound", "keys": "ctrl+alt+8" }, { "command": "unbound", "keys": "ctrl+alt+9" } ```
claunia commented 2026-01-31 04:17:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 5, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Aug 5, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 04:17:27 +00:00
Author
Owner
Copy Link

@zakius commented on GitHub (Aug 5, 2021):

we can't go removing them from the defaults without also blowing them away from anyone who might currently be using them

you can at the first run ask if user wants to keep these I guess? it's hard to discover how to un-break it

and of course don't forget about alt+arrows that also overload terminal input

I think you may consider using super key in all often used shortcuts and some activation/layer switching shortcut using super first for others in future release (next major version so with breaking changes)

@zakius commented on GitHub (Aug 5, 2021): > we can't go removing them from the defaults without also blowing them away from anyone who might currently be using them you can at the first run ask if user wants to keep these I guess? it's hard to discover how to un-break it and of course don't forget about alt+arrows that also overload terminal input I think you may consider using super key in all often used shortcuts and some activation/layer switching shortcut using super first for others in future release (next major version so with breaking changes)
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 Resolution-Duplicate
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#14707
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?