Custom keyboard layouts – keyboard shortcuts work with wrong keys

[ghost]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Keyboard shortcuts work with wrong keys when using custom keyboard layouts.

Steps to Reproduce

1. Install any custom layout (important: not provided by Apple) that keeps original qwerty bindings when command (⌘) is pressed. I will use customised Dvorak ⌘Qwerty for this example.
2. Try using the shortcut for search bar (or any other shortcut).

Expected behavior:

I expected the search bar to open upon clicking qwerty's ⌘F (the fourth key in the middle row, as in Qwerty).

Actual behavior:

The search bar opens upon clicking qwerty's ⌘Y (the sixth key in the top row, as in Dvorak).

Reproduces how often:

Each time.

Versions

Atom 1.40.0 & MacOS Mojave 10.14.5

Additional Information

The issue is not present when using non-customised Dvorak ⌘qwerty layout (like here). In all other apps the problem does not occur neither.

[rsese]

Thanks for the report - just to clarify, was this an issue in previous versions of Atom?

[ghost]

body{font-family:Helvetica,Arial;font-size:13px}I don't know, I started using Atom about two months ago and don't recall having updated it since. dnia 26 sierpnia 2019 o 12:10:08, Robert Sese ([email protected]) napisał: Thanks for the report - just to clarify, was this an issue in previous versions of Atom? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.