Skip to content
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

Support more than two keys for compose #5

Open
GoogleCodeExporter opened this issue Apr 12, 2015 · 0 comments
Open

Support more than two keys for compose #5

GoogleCodeExporter opened this issue Apr 12, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Feature suggestion:

Simplest algorithm would be to search for an exact match, and use it if one is 
found, and if not, do the error sound / leave compose mode if there are no 
prefix matches either.

Avoiding collisions [a compose "ab" and "abc" for example] would simply be done 
by not defining any with collisions [maybe with a warning in the edit window], 
rather than doing anything clever like a delay to wait to see if they're going 
to type "c"

Original issue reported on code.google.com by [email protected] on 16 Feb 2011 at 4:49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant