You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
brandonbeaumia opened this issue
Mar 19, 2024
· 3 comments
Assignees
Labels
blockedBlocked on issues outside of the reasonable control of the kanata projectbugSomething isn't workingllhookPertains to the standard version of Kanata on WindowswindowsIssue pertains to Windows only
When using a config that does not have lshift/rshift in defsrc, navigation keys (arrows/pgdn/etc) used within a layer do not highlight while holding shift.
Relevant kanata config
(defsrc
caps h j k l
)
(deflayer base
@nav h j k l
)
(deflayer navlayer
@base left down up right
)
(defalias base (layer-switch base))
(defalias nav (layer-switch navlayer))
To Reproduce
Set config to above.
Press caps to switch layers.
Hold shift and press navigation keys.
Expected behavior
Text should highlight in the direction of navigation.
Kanata version
kanata v1.6.0-prerelease-1
Debug logs
No response
Operating system
Windows 11
Additional context
Easily worked around after learning the fix, but have not run across documentation about this behavior. Unless fixable, add a note to config.adoc's defsrc entry?
The text was updated successfully, but these errors were encountered:
blockedBlocked on issues outside of the reasonable control of the kanata projectbugSomething isn't workingllhookPertains to the standard version of Kanata on WindowswindowsIssue pertains to Windows only
Requirements
Describe the bug
When using a config that does not have lshift/rshift in defsrc, navigation keys (arrows/pgdn/etc) used within a layer do not highlight while holding shift.
Relevant kanata config
To Reproduce
Expected behavior
Text should highlight in the direction of navigation.
Kanata version
kanata v1.6.0-prerelease-1
Debug logs
No response
Operating system
Windows 11
Additional context
Easily worked around after learning the fix, but have not run across documentation about this behavior. Unless fixable, add a note to config.adoc's defsrc entry?
The text was updated successfully, but these errors were encountered: