I’m seeing an unexpected interaction between Wave and Atuin on macOSEnvironment
.7.5 (arm64)
Wave version: latest stable (auto‑update enabled) Shell: Client Version 0.14.5 (202604161535)
Atuin installed and initialized via eval "$(atuin init bash)" in .bashrc
Issue
In Wave’s terminal, when I use the mouse wheel to scroll up/down to view previous terminal output, Wave opens the Atuin history UI instead of simply scrolling the buffer.
Important details:
Atuin is correctly bound to the Up arrow key (pressing Up opens Atuin history, as expected).
In a regular terminal (non‑Wave), the mouse wheel only scrolls the terminal output and does not open Atuin.
This behavior only appears inside Wave terminal.
I did not knowingly configure any mouse bindings in Wave to open Atuin or history search.
It looks like Wave is treating mouse wheel scroll events as a history‑search trigger (possibly emulating Up key presses), which conflicts with Atuin’s binding.
Expected behavior
Mouse wheel scroll should only scroll the terminal’s scrollback, like a normal terminal.
Atuin history should open only when I press the Up arrow (or whatever explicit keybinding I configure), not on mouse wheel events.
Questions
Is there currently a setting in Wave to disable this “scroll to open history” behavior or to unbind mouse wheel from any history/search action?
If not, could you consider:
A toggle to disable any mouse‑driven history behavior, or
Ensuring mouse wheel events are passed through as pure scroll events, without synthesizing Up/Down key presses?
I’m happy to provide logs, screenshots of settings, or try a test build if that helps.
Thanks!
I’m seeing an unexpected interaction between Wave and Atuin on macOSEnvironment
.7.5 (arm64)
Wave version: latest stable (auto‑update enabled) Shell: Client Version 0.14.5 (202604161535)
Atuin installed and initialized via eval "$(atuin init bash)" in .bashrc
Issue
In Wave’s terminal, when I use the mouse wheel to scroll up/down to view previous terminal output, Wave opens the Atuin history UI instead of simply scrolling the buffer.
Important details:
Atuin is correctly bound to the Up arrow key (pressing Up opens Atuin history, as expected).
In a regular terminal (non‑Wave), the mouse wheel only scrolls the terminal output and does not open Atuin.
This behavior only appears inside Wave terminal.
I did not knowingly configure any mouse bindings in Wave to open Atuin or history search.
It looks like Wave is treating mouse wheel scroll events as a history‑search trigger (possibly emulating Up key presses), which conflicts with Atuin’s binding.
Expected behavior
Mouse wheel scroll should only scroll the terminal’s scrollback, like a normal terminal.
Atuin history should open only when I press the Up arrow (or whatever explicit keybinding I configure), not on mouse wheel events.
Questions
Is there currently a setting in Wave to disable this “scroll to open history” behavior or to unbind mouse wheel from any history/search action?
If not, could you consider:
A toggle to disable any mouse‑driven history behavior, or
Ensuring mouse wheel events are passed through as pure scroll events, without synthesizing Up/Down key presses?
I’m happy to provide logs, screenshots of settings, or try a test build if that helps.
Thanks!