Arabic, Chinese, Hebrew, Russian among others.
When set to different layout many apps ignore common actions like Cmd/Ctrl + C and you need to make sure you're using a latin layout.
121–130 of 212 posts
Arabic, Chinese, Hebrew, Russian among others.
When set to different layout many apps ignore common actions like Cmd/Ctrl + C and you need to make sure you're using a latin layout.
It really surprised and disappointed me recently that native macOS apps have the same problem outlined here. For example, the standard system-wide ‘back’ shortcut (e.g. in Safari, Finder, Preview) is Cmd+[, but this is inoperable in many keyboard layouts that don’t have any key that produces [ without modifiers. (For context: I was writing a simple mouse gestures utility that sends that keyboard shortcut to accomplis…
On a tangent, why are non-qwerty keyboards so poorly designed for programming? And specifically, why is apple’s azerty layout so terrible? Just look at this image: https://i.stack.imgur.com/3LL8a.png Can you find the [ and ] keys? If you’re having trouble, it’s because you have to use 2 (two!) modifier keys and activate the ( or ) keys, which themselves are clumsily placed. This cannot be typed one-handed in a comfor…
It's the other way around. The keyboard was the foundation for the programming languages and shortcuts, like moving with hjkl in vim. No German keyboard user would have created a language like C with curly braces, when you would break your fingers typing this (alt 8 is {, alt 9 is }, and alt+5 is [, alt+6 is ] ). I use a US keyboard for that exact reason
Original keyboards (up until 1980s) had special polish letters like ąęśćżń on dedicated keys, and various characters like [{$ moved around.
That is called „Polish” layout.
Then, since 1990 we have „Polish (programmer’s)” , which is essentially the american keyboard and local characters hidden under alt-right.
Literally everyone uses „Polish (programmers)” now, and you just need to remember to choose this, and not the regular „Polish” in system settings :)
There is also a whole slew of issues with Polish characters. Polish keyboard setup relies on "right-alt" and a letter to get it's diacritics variation. Ie: 'ą' is 'right-alt'+a Windows for backwards compatibility reports 'right-alt' as 'alt+control'. Many applications developers assign key combos with no negative checks. So 'ctrl-s', typically used for save gets triggered when user wants to type 'ś'. To repeat, "righ…
Earlier quoted context omitted.
Seems easy to fix > Windows for backwards compatibility reports 'right-alt' as 'alt+control'. There’s your problem, right there
The backwards compatibility is for physical keyboards. So that a keyboard with just one alt can still trigger polish letters. I don't know how other OSes allow for users to trigger "right-alt" when the keyboard has only one alt character.
I actually do this on two-alt keyboards too, because I like to use either alt for shortcuts.
It would be nice if keyboard shortcuts were a matter of the OS and applications would expose a list of all available commands with default shortcuts...
Don't like the dead keys, but the shortcut confusion is worse.
In order to write backtick, I have to shift-click the key left to backspace and then click spacebar. Tilde ~ is similar: option-click and then space. This makes the out-of-the-box keyboard shortcut for switching window on macOS unreachable on my macbook pro. There are several default shortcuts on osx that are unreachable from international keyboards.
TL;DR. Don't use keypress, it's deprecated. Don't use 'keyCode', 'which', 'char' which are all deprecated. Do use 'key' Another issue I run into is forms that dismiss via keydown and escape. I type in Japanese which means I'm using an IME. An IME, or at least the Japanese IME, you type characters and they appear with possible completions. They haven't actually been given to the app yet. Pressing Escape cancels the co…