microsoft/Terminal

Binding the `§` key to actions does not work, only the equivalent Ctrl-Alt-5§§

Open

#18,663 opened on Mar 8, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (3,212 forks)batch import
Area-SettingsUIHelp WantedIssue-BugNeeds-Tag-FixProduct-Terminal

Repository metrics

Stars
 (35,764 stars)
PR merge metrics
 (Avg merge 27d 19h) (24 merged PRs in 30d)

Description

Windows Terminal version

1.21.10351.0

Windows build number

10.0.26100.3323

Other Software

No response

Steps to reproduce

  1. Use a Swiss German keyboard, and the corresponding Swiss German keyboard layout
  2. Just to check: Press the § key while focussing a text field, and see an § appear. Press Ctrl-Alt-5, and the same § should appear.
  3. Bind the quakeMode action to § with the Terminal Settings window.

Expected Behavior

Pressing the § opens a quake mode window.

Actual Behavior

  1. Pressing the § key does not open a quake mode window.
  2. Pressing the (equivalent) Ctrl-Alt-5 does open a quake mode window.

A new section appears in settings.json with these contents:

        {
            "command": 
            {
                "action": "quakeMode"
            },
            "keys": "\u00a7"
        },

Contributor guide

Research direction
Trace the key binding handling code to identify why the `§` key is not recognized as a key while Ctrl Alt 5 is, focusing on how key identifiers are parsed and compared.
Tech stack
cpp
Domain
desktopcli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70