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
Thank you for this TPM plugin! I had been thinking about all of the different ways I could bullet-proof my tmux scrolling hack I made a while ago, the main idea was to contextually enable the ability to scroll up in history in a shell (which isn't in alternate window mode) via copy-mode and to naturally pass the event on into alternate window mode programs that enable mouse mode such as vim, and to emulate arrow keys when the alternate mode program doesn't enable mouse mode, such as less. This makes for perfect UX.
This is exactly what you have done and it is a beautiful thing, we can even configure exactly whether doing so in a different pane yanks focus to it or not. I love it so much.
Now, another concept that I was toying with in my mind is some method of addressing the disparity in when I change between using a mouse (with discrete clicks) and a Mac touchpad, which is able to give the control of individual scroll clicks but also effortlessly flick to spam a lot of events.
So far we have config here letting us choose how many lines to scroll for scroll wheel emulation for the copy-mode scrolling and alternate mode arrow key emulation, this is a linear one to one relationship to the mouse event. I was hoping that maybe we could have a configuration that allows for acceleration here. As we rapidly send a lot of wheel events it can increase how many lines each event moves. This will make it more effortless to traverse larger distances with a traditional mouse wheel.
A drawback might be that on a platform such as macOS the end result is the combination of two scrolling acceleration behaviors. I was going to use differing config between my different platforms though, it should address that issue.
The text was updated successfully, but these errors were encountered:
unphased
changed the title
Feature request for comment, related to mouse wheel -> arrow emulation
Feature request for comments, related to mouse wheel -> arrow emulation
Jan 4, 2018
unphased
changed the title
Feature request for comments, related to mouse wheel -> arrow emulation
Feature request for comments: Acceleration in mouse wheel -> arrow emulation
Jan 4, 2018
Thank you for this TPM plugin! I had been thinking about all of the different ways I could bullet-proof my tmux scrolling hack I made a while ago, the main idea was to contextually enable the ability to scroll up in history in a shell (which isn't in alternate window mode) via copy-mode and to naturally pass the event on into alternate window mode programs that enable mouse mode such as vim, and to emulate arrow keys when the alternate mode program doesn't enable mouse mode, such as less. This makes for perfect UX.
This is exactly what you have done and it is a beautiful thing, we can even configure exactly whether doing so in a different pane yanks focus to it or not. I love it so much.
Now, another concept that I was toying with in my mind is some method of addressing the disparity in when I change between using a mouse (with discrete clicks) and a Mac touchpad, which is able to give the control of individual scroll clicks but also effortlessly flick to spam a lot of events.
So far we have config here letting us choose how many lines to scroll for scroll wheel emulation for the copy-mode scrolling and alternate mode arrow key emulation, this is a linear one to one relationship to the mouse event. I was hoping that maybe we could have a configuration that allows for acceleration here. As we rapidly send a lot of wheel events it can increase how many lines each event moves. This will make it more effortless to traverse larger distances with a traditional mouse wheel.
A drawback might be that on a platform such as macOS the end result is the combination of two scrolling acceleration behaviors. I was going to use differing config between my different platforms though, it should address that issue.
The text was updated successfully, but these errors were encountered: