Hi! I use this app for homerow chord modifiers. I also use neovim as my daily editor, together with the vim-arpeggio plugin for vim specific chord keybinds.
Here's the issue I am facing:
Let's say I register a jl chord using simultaneous inside this app
I then register a jk chord using vim-arpeggio
When I press kj really quickly, the j will have a tiny delay (which is understandable, there's no other way to detect simultaneous key presses), meaning vim-arpeggio won't register the keys as pressed in quick succession.
It works fine if I press the keys in reverse order.
Expected behaviour:
After using simultaneous anywhere, all keys should have an artificial delay, even if it serves no other purpose than consistency (this could be a config option). On my linux setup, I have a custom python script which does exactly this, and it works very well!
I know I could maybe replace vim-arpeggio with this app, but I want my neovim config to remain os-agnostic.
Hi! I use this app for homerow chord modifiers. I also use neovim as my daily editor, together with the vim-arpeggio plugin for vim specific chord keybinds.
Here's the issue I am facing:
When I press kj really quickly, the j will have a tiny delay (which is understandable, there's no other way to detect simultaneous key presses), meaning vim-arpeggio won't register the keys as pressed in quick succession.
It works fine if I press the keys in reverse order.
Expected behaviour: After using simultaneous anywhere, all keys should have an artificial delay, even if it serves no other purpose than consistency (this could be a config option). On my linux setup, I have a custom python script which does exactly this, and it works very well!
I know I could maybe replace vim-arpeggio with this app, but I want my neovim config to remain os-agnostic.