u9OEYkI0bUxuGns

5 ms·

1.
by u9OEYkI0bUxuGns 3y ago
>OK so what is the ideal solution in your opinion? Cheeky answer: The ideal solution is a smartphone. It has no keyboard. You don't have to worry about keybindings at all anymore. Real answer: There isn't one. Once apps can do
2.
by u9OEYkI0bUxuGns 3y ago
>But it mostly didn’t, it was generally good enough, and when it did it commonly pointed to a bug in the app anyway That hasn't changed though? The individual settings might have changed. Some were added and some were taken away, as
3.
by u9OEYkI0bUxuGns 3y ago
>Yes you absolutely can. I've tried it and you can rebind copy/paste/undo/etc globally to use Ctrl-c/Ctrl-v/Ctrl-z/etc, using the builtin Settings.app. It takes about a minute or two, a bit more if you
4.
by u9OEYkI0bUxuGns 3y ago
>The concept was never broken on macOS Yes it is, MacOS also doesn't have key themes. I can't reconfigure a Mac to use Windows keyboard shortcuts. Those are just the default key bindings every Mac app has to support. That'
5.
by u9OEYkI0bUxuGns 3y ago
>You’re viewing things from the wrong angle. Nope, the onus is always on the app developer. Even Microsoft is inconsistent with their own Windows apps using overlay scrollbars. Old Windows apps don't have them, but the new app gui
6.
by u9OEYkI0bUxuGns 3y ago
This comment is not correct. GNOME Foundation didn't co-opt or sabotage GTK. For a very long time it's just been mostly GNOME people contributing. It's a known problem that GTK needs more people contributing to fix issues on
7.
by u9OEYkI0bUxuGns 3y ago
Nothing was sabotaged there. Custom key themes were removed because the whole concept of them was broken. The only one anyone ever seemed to use was the Emacs theme and that just broke apps because they didn't handle the case when an E