Skip to content

Setting 'altGrAliasing' to 'false' disables AltGr #7372

Closed

Description

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2233.0

Any other software? No

Steps to reproduce

  1. Open Windows Terminal
  2. Edit its settings and set altGrAliasing to false in profiles/default
  3. Switch back to Windows Terminal and try to enter a character via AltGr+...

Expected behavior

The appropriate character should appear.

Actual behavior

Nothing is written.

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Aug 22, 2020
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Aug 22, 2020
  3. DHowett commented on Aug 24, 2020

    @DHowett
    Member

    What keyboard layout are you using? Is it custom or did it come with Windows?

  4. skrysm commented on Aug 25, 2020

    @skrysm
    Author

    Dustin L. Howett (@DHowett) I'm using the regular German keyboard layout that came with Windows.

  5. ghost added
    Needs-AttentionThe core contributors need to come back around and look at this ASAP.
    on Aug 25, 2020
  6. ghost removed
    Needs-Author-FeedbackThe original author of the issue/PR needs to come back and respond to something
    on Aug 25, 2020
  7. zadjii-msft commented on Aug 25, 2020

    @zadjii-msft
    Member

    I suppose the next thing to do with this is

    /summon Leonard Hecker (@lhecker)

  8. lhecker commented on Aug 25, 2020

    @lhecker
    Member

    This is missing a && !states.IsAltGrPressed().

  9. added
    Area-InputRelated to input processing (key presses, mouse, etc.)
    Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    and removed
    Needs-AttentionThe core contributors need to come back around and look at this ASAP.
    on Aug 25, 2020
  10. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Aug 25, 2020
  11. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Aug 25, 2020
  12. ghost added
    In-PRThis issue has a related PR
    on Aug 25, 2020
  13. ghost closed this as completedin #7400on Aug 25, 2020
  14. ghost removed
    In-PRThis issue has a related PR
    on Aug 25, 2020
  15. ghost added a commit that references this issue on Aug 25, 2020
    ac310d9
  16. ghost added
    Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.
    on Aug 25, 2020
  17. added 2 commits that reference this issue on Aug 25, 2020
    7967e17
    be50003
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area-InputRelated to input processing (key presses, mouse, etc.)Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issue-BugIt either shouldn't be doing this or needs an investigation.Product-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions