tmux doesn't support \033[?1001s, adding that may be enough
if not then ncurses needs to tell tmux it is using the mouse like
ncmpcpp is doing, are you sure it isn't sending \033[?1000h? (run one of
the applications in script, or use tmux logging to see)
On Fri, Jun 03, 2011 at 04:08:04PM +0200,
> haven't got time to look into this really, but it is on the pile in my
> inbox so if nobody else does I'll get to it after this week
Ok i have wasted couple of hours investigating this and conclusion is as
follows.
If any mouse-interactivity feature (f.e. mouse-select-pane) is turned on
(and, i
haven't got time to look into this really, but it is on the pile in my
inbox so if nobody else does I'll get to it after this week
On Mon, May 23, 2011 at 08:05:52PM +0200, marcel partap wrote:
> Salut :)
> umm... while you have merged my patch for window scrolling (thaanx :D), the
> issue with
Salut :)
umm... while you have merged my patch for window scrolling (thaanx :D), the
issue with wheel events being not correctly passed when
either mouse-select-window or mouse-select-pane is turned on persists. Can you
reproduce that?
> 1) open less with text +1 page, scroll mouse.
> 2) toggle
> I don't follow, what is the problem? If you turn on mouse-select-pane it
> eats the scroll wheel button events?
no, it seems to alter them. ncmpcpp reacts on wheel events, less not.
> I think it would be better for scroll wheel to select panes not
> windows.
The patch only enables mouse wheel wi
Hi
I don't follow, what is the problem? If you turn on mouse-select-pane it
eats the scroll wheel button events?
I think it would be better for scroll wheel to select panes not
windows. Maybe it is about time we had mouse-button-1-command options
etc...
On Thu, Apr 28, 2011 at 05:33:41PM +0200,
