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
xudyang1 opened this issue
Jan 2, 2025
· 2 comments
Assignees
Labels
bugSomething isn't workingllhookPertains to the standard version of Kanata on WindowsquestionFurther information is requestedwindowsIssue pertains to Windows only
type ctrl+shift+1 to open a new tab with profile index 1
type any keys to see the output (e.g., type abcd, but ABCD shown on the screen).
disable process-unmapped-keys fixes it config.kbd:
(defsrc)
(deflayermap (base)
caps esc
esc `
)
Expected behavior
should not shift keys
Kanata version
1.7.0
Debug logs
No response
Operating system
windows 10
Additional context
When keys are shifted, alt+tab twice (switch to another program and switch back) temporarily fixes the shift. Typing ctrl+shift+1 and the bug occurs again.
The text was updated successfully, but these errors were encountered:
Does this still reproduce if you try winiov2 variant?
jtroo
added
question
Further information is requested
windows
Issue pertains to Windows only
llhook
Pertains to the standard version of Kanata on Windows
labels
Jan 3, 2025
bugSomething isn't workingllhookPertains to the standard version of Kanata on WindowsquestionFurther information is requestedwindowsIssue pertains to Windows only
Requirements
Describe the bug
process-unmapped-keys
keeps shifting keys after pressingctrl+shift+number
in windows terminal.Relevant kanata config
No response
To Reproduce
config.kbd
:kanata -c config.kbd
ctrl+shift+1
to open a new tab with profile index 1abcd
, butABCD
shown on the screen).process-unmapped-keys
fixes itconfig.kbd
:Expected behavior
should not shift keys
Kanata version
1.7.0
Debug logs
No response
Operating system
windows 10
Additional context
When keys are shifted,
alt+tab
twice (switch to another program and switch back) temporarily fixes the shift. Typingctrl+shift+1
and the bug occurs again.The text was updated successfully, but these errors were encountered: