-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customizing and sorting Quick Accent #20393
Comments
Agreed. Being able to add to the list of characters on (say) "c" to include ©, and to be able to move that to the "best" (for me) location in the list would be most welcome user customization (because you'll never be able to satisfy everyone). |
Definitely this. It would let me solve a longstanding problem I have with the poor keyboard layout in my language, where the diacritics, braces and parentheses put a lot of strain in a touch typist's hands. It would also override the need for #20390 and would allow us to be way more productive. EDIT: |
Another request to edit Quick Accent order: #20407 |
I agree. Here's a further idea. |
Still no such option two years after?? wtf?? |
Description of the new feature / enhancement
In addition to important language related characters like mentioned here #20390
it would be great if users could sort the order in which characters are listed in the pop-up, and if you could customize characters and the keys they are shown on.
For example, if you could freely map symbols like "©" to any regular key on the keyboard.
Scenario when this would be used?
If you make use of specific accents frequently, the fixed order in which characters currently appear in might be counterintuitive and counterproductive. Being able to change the order in which they appear could allow each user to put frequently used characters at the front of the list.
Being able to assign custom characters to keys would be a major improvement for ease of use, compared to remembering and using Alt-codes or creating lists of characters to pick and copy-paste from.
Supporting information
No response
The text was updated successfully, but these errors were encountered: