Skip to content

[bug] Mac: Control+<Key> shortcuts are broken in 1.5.0 #3370

Closed as duplicate

Description

@Craga89

Describe the bug

Prior to 1.5.0, my Control+R (and similar) keyboard shortcuts worked fine in the terminal. Now, they don't trigger anything.

Verifiications

  • Terminal shortcuts are working on iTerm and others.
  • Downgraded to 1.4.7 and verified they work correctly

Activity

  1. changed the title [-][bug] Control+<Key> shortcuts are broken in 1.5.0[/-] [+][bug] MAC: Control+<Key> shortcuts are broken in 1.5.0[/+] on Apr 12, 2026
  2. changed the title [-][bug] MAC: Control+<Key> shortcuts are broken in 1.5.0[/-] [+][bug] Mac: Control+<Key> shortcuts are broken in 1.5.0[/+] on Apr 12, 2026
  3. added a commit that references this issue on Apr 12, 2026
  4. rube-de commented on Apr 12, 2026

    @rube-de

    it also broke my copy paste with my keyboard layout via karabiner elements

  5. transcendr commented on Apr 12, 2026

    @transcendr

    Came here to report this. The application has become unusable.

  6. ucheol2 commented on Apr 13, 2026

    @ucheol2

    Also my short cuts with cmd + shift + [ (previous tab), cmd + shift + ] (next tab) are broken

  7. tobalsan commented on Apr 13, 2026

    @tobalsan

    +1

    ⌘+v just prints v.

  8. Craga89 commented on Apr 14, 2026

    @Craga89
    Author

    This seems to be addressed in 1.5.1 onwards FYI

  9. rube-de commented on Apr 18, 2026

    @rube-de

    This seems to be addressed in 1.5.1 onwards FYI

    shortcuts are still broken, my layout has V on W, using cmd + V it will still trigger the cmd+w shortcut.
    I have to remove / change the close tab shortcut to be able to use cmd+v paste.

  10. Kitenite commented on May 6, 2026

    @Kitenite
    Member

    Related reports (cross-referenced during issue triage — same area, may or may not share a root cause):

  11. Kitenite commented on Jul 11, 2026

    @Kitenite
    Member

    Closing as a duplicate of #5598, the consolidated tracker for stale keyboard-shortcuts issues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5598 and we'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions