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
{{ message }}
Repository navigation
Default repeat_delay = 250 causes duplicated characters during normal typing (Parallels VM guest) #8760
Keyboard:at-translated-set-2-keyboard (internal, via Parallels)
What's wrong?
The default repeat_delay = 250 in default/hypr/input.lua causes duplicated
characters during ordinary typing on this system. Normal typing produces output
like helllo / commmand several times per paragraph.
#5293 set this value, stating: "In my testing, this is the lowest you can go
without causing any issues with double key presses." This report is a
counter-example to that premise — at 250ms, ordinary keystroke dwell time
crosses the repeat threshold, and repeat_rate = 40 then emits a burst rather
than a single extra character, so each trip is very visible.
Caveat, stated up front: this is a Parallels VM guest. Keystroke timing
passes through the hypervisor and may jitter more than on bare metal, so this
may be specific to virtualized guests rather than universal. I have not been
able to test the same config on bare metal. Flagging it because Omarchy in a
Parallels/UTM VM is a common way to evaluate the distro, and the current default
makes typing unreliable there out of the box.
Steps to reproduce
Install Omarchy 4.0.1 in a Parallels VM (defaults, no input customization).
Type normal prose in any application.
Observe duplicated letters at a rate of roughly a few per paragraph.
Expected
Default settings should not produce duplicated characters during normal typing.
Workaround
Raising the delay in ~/.config/hypr/input.lua fixes it completely:
repeat_delay is the significant one; 500 improved things noticeably and 600
eliminated the duplication entirely.
Suggestion
The tradeoff in #5293 is real — a long delay does make held-key deletion and vim
motions feel sluggish. But the two goals are separable: repeat_delay controls
how easily repeat is triggered accidentally, while repeat_rate controls how
fast it goes once deliberately triggered. Raising the delay toward 400-500 while
keeping the rate high would preserve most of the fast-hold benefit that #5293
wanted, with a much smaller accidental-trigger window.
Checked against quattro (c352b62) by Opus 5.5, with a second opinion from Codex Medium. Codex reached the same conclusion; it read the same repository, so its independence is not guaranteed.
What the code does. The defaults are still repeat_rate = 40 and repeat_delay = 250 in default/hypr/input.lua:60-61, set by #5293. These are configuration values, not a defect in Omarchy's code: a key that is still logically held 250 ms after it went down starts repeating, and at 40/s each extra character follows about 25 ms later, which is why a single trip shows up as lll rather than ll. Your override in ~/.config/hypr/input.lua is the supported way to change it, and it is loaded after the defaults (config/hypr/hyprland.lua).
Why a VM would matter. Latency that delays key-down and key-up by the same amount does not change how long a key reads as held, so general hypervisor lag alone would not cause this. The release event has to arrive late, or be processed late, relative to the press. That is plausible for a Parallels guest but not established. Omarchy already detects VMs (bin/omarchy-hw-vm) and uses it at install to turn off animations (install/user/hardware/vm-no-animations.sh), but makes no input adjustment there.
Not reproduced. A QEMU worker can show that a 350 ms hold repeats at 250 and not at 600, but that is true by definition and says nothing about Parallels, whose host keyboard path a QEMU guest does not go through. No duplicate or competing fix is open. #7806 suppresses repeat in the lock screen's password field only.
What would settle the cause: in the affected guest, run wev (or sudo libinput debug-events --show-keycodes), type until a letter doubles, and paste the press and release lines for that key. If the release lands more than 250 ms after the press while you tapped normally, the hypervisor is delaying releases.
What happens next: whether to raise the default, or only on VMs, is a trade-off against the held-key responsiveness #5293 was after. That is the maintainer's decision, and this issue is waiting on them.
Activity
omarchybot commentedon Oct 9, 2026
Checked against
quattro(c352b62) by Opus 5.5, with a second opinion from Codex Medium. Codex reached the same conclusion; it read the same repository, so its independence is not guaranteed.What the code does. The defaults are still
repeat_rate = 40andrepeat_delay = 250indefault/hypr/input.lua:60-61, set by #5293. These are configuration values, not a defect in Omarchy's code: a key that is still logically held 250 ms after it went down starts repeating, and at 40/s each extra character follows about 25 ms later, which is why a single trip shows up aslllrather thanll. Your override in~/.config/hypr/input.luais the supported way to change it, and it is loaded after the defaults (config/hypr/hyprland.lua).Why a VM would matter. Latency that delays key-down and key-up by the same amount does not change how long a key reads as held, so general hypervisor lag alone would not cause this. The release event has to arrive late, or be processed late, relative to the press. That is plausible for a Parallels guest but not established. Omarchy already detects VMs (
bin/omarchy-hw-vm) and uses it at install to turn off animations (install/user/hardware/vm-no-animations.sh), but makes no input adjustment there.Not reproduced. A QEMU worker can show that a 350 ms hold repeats at 250 and not at 600, but that is true by definition and says nothing about Parallels, whose host keyboard path a QEMU guest does not go through. No duplicate or competing fix is open. #7806 suppresses repeat in the lock screen's password field only.
What would settle the cause: in the affected guest, run
wev(orsudo libinput debug-events --show-keycodes), type until a letter doubles, and paste the press and release lines for that key. If the release lands more than 250 ms after the press while you tapped normally, the hypervisor is delaying releases.What happens next: whether to raise the default, or only on VMs, is a trade-off against the held-key responsiveness #5293 was after. That is the maintainer's decision, and this issue is waiting on them.