Ækeynox
The Symbols layer is messed up
There are two probable causes:
- Kanata, KMonad, Keyd or another similar service is running (easy fix)
- your Selenium implementation has not been configured for the host keyboard layout.
Symbols are sent as key codes, not characters. By default, Ækeynox assumes the host computer is configured in US QWERTY; if not, make sure the proper layout has been selected in your Ækeynox settings.
Besides, most non-ASCII keyboard layouts behave differently, depending on the host OS.
By default, Ækeynox expect the host to be a PC; if not, make sure the MACOS
flag is set.
Shortcuts in the Navigation layer don’t work as expected
Same probable causes and fixes as for Symbols (above): make sure Kanata isn’t running, and check the host layout/OS configuration.
Will ZSA/Oryx or MoErgo Layout Editor be officially supported?
Unlikely: we focus on free/libre software, and we don’t see how the various configuration options could be implemented in these proprietary tools.
Under the hood, Oryx and MoErgo Layout Editor are based on QMK and ZMK, respectively; as we have Ækeynox implementations for both of them, we’ll rather support ZSA and MoErgo keyboards in Ækeynox. We don’t see any use case where our implementations would lack anything compared to their commercial alternatives; please open a ticket if you think otherwise.
Keymap
[TT] How do I do a Ctrl-Backspace?
In Thumb-Taps mode, Ctrl‑Space is mapped to Ctrl‑Backspace.
[HRM] I find HRMs error-prone, should I enable PERMISSIVE_HOLD?
TL;DR: no. Especially if you struggle with home row mods, e.g. trigging unwanted modifiers as you type some text.
As far as we know, this advice was relevant back in the days when QMK’s default behavior
for mod-taps was “hold-preferred”: the “permissive hold” alternative was less
error-prone for home row mods. Via and/or Vial might still have this “hold-preferred”
default, but QMK has used “tap-preferred” by default for a long time now — and activating
PERMISSIVE_HOLD would increase the count of false positives.
Ækeynox is very opiniated on timing priorities, and sets a
“tap-preferred” priority for home row mods along with a high TAPPING_TERM
(300 ms), which is a very safe default for beginners and fast typists, but forces to slow
down to use modifiers.
There are several ways to deal with this delay for modifiers:
- consider it’s a feature: the intention must be expressed (and we strongly recommend this approach)
- use an alternative navigation layer relying on Callum mods, which is a very safe alternative to mod-taps
- use advanced timing options à la
PERMISSIVE_HOLD, along with mitigation measures to limit false positives- QMK:
PERMISSIVE_HOLD+ Accordion-like safeguards: chordal hold (supported by Vial and Oryx), speculative hold, flow tap… - ZMK: “balanced” behavior + positional hold-tap configuration or timeless HRMs.
- QMK:
Both features are planned:
- a Callum-style navigation layer is already experimented in the ZMK implementation
- an option à la “permissive hold” will be proposed, unset by default.