-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[KBM] Chord key support #4508
Comments
Hi @saahmedm, what I meant is this: https://en.wikipedia.org/wiki/Dead_key |
So my understanding is supporting dead keys = chords? is there a difference in implementation, other than a specific key being chosen as the "dead key" that initiates the chord shortcut. |
I guess dead keys can be seen as a simplified version of a chord, in which the second keystroke should be a simple keypress and not another combination. |
@Canna71 which keyboard layout would you be using for such a remapping? |
English US
Why?
Il 16 lug 2020, 18:47 +0200, Arjun Balgovind <[email protected]>, ha scritto:
… @Canna71 which keyboard layout would you be using for such a remapping?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Updating the title here to crisply state chords |
Closing in favor of #6976 |
not totally sure why chords was closed out. Could have been for dead key support. Lets make this dedicated for just chords |
This has been worked on during the 0.79.0 release cycle. |
Hi, I think it should be useful to add support for dead keys, or even chords.
For example, I am currently using Autohotkey to insert accented letters by typing, for example
Alt+`, A
=>à
Pressing Alt+` will not map to any key (thus, a dead key) but will enter a mode, after which the mapping is applied (in this case a=>à)
If KBM was going to support this, I could ditch Autohotkey.
The text was updated successfully, but these errors were encountered: