Place - and _ next to each other on the symbols page - #2630
Conversation
The hyphen and underscore keys were separated by & in the second row of the symbols layout (@ # $ _ & - + ( ) /). As two closely related characters, they are easier to reach when placed side by side, so swap & and - to get @ # $ _ - & + ( ) /. Same change for the Arabic symbols layout, which mirrors the default one. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Did anyone actually request this change or have issues with the current default layout? |
|
Fair point — it was a concrete user request (having - and _ next to each other), but you're right that swapping & and - in the shared default trades one group's muscle memory for another's, and that's not a good deal. I've come to think the underlying problem isn't the order of two keys but that the symbols page is US-shaped for everyone. On a German physical keyboard, - and _ literally share one key (_ is Shift+-), which is why this felt wrong to the user in the first place. So I'm closing this in favour of #2681, which gives each region the symbols arrangement its users already know from their physical keyboard — including _ next to - in the regional rows — while leaving the default page exactly as it is for everyone else. |
What
Swap the
&and-keys in the second row of the symbols layout so the hyphen and underscore sit side by side:@ # $ _ & - + ( ) /@ # $ _ - & + ( ) /The same swap is applied to the Arabic symbols layout (
symbols_arabic.txt), which mirrors the default one.Why
-and_are two closely related characters (both are horizontal-line glyphs, both are common in identifiers, filenames, handles, etc.). Having them next to each other makes the second one reachable without hunting across the row; previously&sat between them.Notes
-keeps– ⁻ — ·,_keeps% ‰)../gradlew :app:testRunTestsUnitTest --tests "helium314.keyboard.ParserTest"passes (42/0/0);parseExistingLayoutsreads and validates the modified files andcanLoadKeyboardbuilds a keyboard from them.