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
Is your feature request related to a problem? Please describe.
I have been using Wezterm's keybinds, among which its ScrollByPage binds shift+PageUp and shift+PageDown.
i couldn't help but to feel tho that these binds made for sort of disparate UX with paging binds used in applications (e.g. less / vim), which would tend to just respond to PageUp/PageDown directly.
however, i found that if i were to assign ScrollByPage binds to PageUp/PageDown directly, only wezterm would still respond to it, yet the applications wouldn't anymore.
Describe the solution you'd like
allow sharing binds like PageUp/PageDown between wezterm and applications, similar to how both might respond to scrolling by mouse or touchpad.
Describe alternatives you've considered
use different keybinds for the terminal versus applications, making for a less intuitive UX
Is your feature request related to a problem? Please describe.
I have been using Wezterm's keybinds, among which its
ScrollByPage
binds shift+PageUp and shift+PageDown.i couldn't help but to feel tho that these binds made for sort of disparate UX with paging binds used in applications (e.g.
less
/ vim), which would tend to just respond to PageUp/PageDown directly.however, i found that if i were to assign
ScrollByPage
binds to PageUp/PageDown directly, only wezterm would still respond to it, yet the applications wouldn't anymore.Describe the solution you'd like
allow sharing binds like PageUp/PageDown between wezterm and applications, similar to how both might respond to scrolling by mouse or touchpad.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: