^[[A and ^[[B are up and down and tmux won't generate them for scroll events so the terminal must be doing it for one or another mode
when mouse-select-pane is on and there are panes, the terminal should always be in mouse input mode, when mouse-select-pane is off it should only be in mouse input mode when thet application requests it maybe it is the wrong way round somewhere, i'll have to have a look, probably over the weekend On Fri, Sep 03, 2010 at 04:20:42PM +0200, Mika Fischer wrote: > The output is the same as with mouse-select-pane on... > > Maybe the printf changes something that makes the two cases behave the > same. Because after the printf, the scroll events don't cycle through > the command history in bash anymore, even when mouse-select-pane is > off. Before the printf, the wheel events work fine. > > Yes, when I just do cat without the printf before, I get the following: > In the cases tmux one pane (m-s-p on or off) and tmux multi-pane with m-s-p > off: > scroll up: ^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A > scroll down: ^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B > click: nothing > > With tmux multi-pane and m-s-p on: > scroll up: nothing > scroll down: nothing > click: nothing > > Without tmux: > scroll up: nothing > scroll down: nothing > click: nothing > > So there's definitely some different behavior with m-s-p on. I don't > know why without tmux nothing gets displayed. I don't know much about > terminals though. I hope you can make something of this... > > Best, > Mika > > On Fri, Sep 3, 2010 at 16:04, Nicholas Marriott > <nicholas.marri...@gmail.com> wrote: > > what output do you get with it off doing the same test? > > > > > > On Fri, Sep 03, 2010 at 03:24:32PM +0200, Mika Fischer wrote: > >> No, the problem only happens when mouse-select-pane is on. If it's > >> off, everything works as it should. > >> > >> On Fri, Sep 3, 2010 at 15:17, Nicholas Marriott > >> <nicholas.marri...@gmail.com> wrote: > >> > yes, probably, do you get the same with mouse-select-pane on and off? > >> > > >> > > >> > On Fri, Sep 03, 2010 at 03:09:19PM +0200, Mika Fischer wrote: > >> >> But the scrolling works fine if there's only one pane or when > >> >> mouse-select-pane is off. So there must be something different when > >> >> using multiple panes in conjunction with mouse-select-pane, right? > >> >> > >> >> On Fri, Sep 3, 2010 at 15:06, Nicholas Marriott > >> >> <nicholas.marri...@gmail.com> wrote: > >> >> > The first character after the [M is the buttons and tmux is outputting > >> >> > the same thing in all cases, so the problem is less or whatever. Maybe > >> >> > it only listens for mouse clicks when TERM=xterm or something silly > >> >> > like > >> >> > that. > >> >> > > >> >> > > >> >> > On Fri, Sep 03, 2010 at 02:51:12PM +0200, Florian CROUZAT wrote: > >> >> >> > >> >> >> On 3 sept. 2010, at 14:38, Nicholas Marriott wrote: > >> >> >> > >> >> >> > what happens if you do printf "\033[?1000h" then cat and scroll the > >> >> >> > wheel, inside and outside tmux? > >> >> >> > >> >> >> With mouse-select-pane on (tmux1.3+Terminal.app+mouseterm: plugin to > >> >> >> give Terminal.app mouse support) > >> >> >> > >> >> >> Outside tmux: > >> >> >> ?? ?? ?? scroll-up: ^[[M`"E^[[M`"E > >> >> >> ?? ?? ?? scroll-down: ^[[Ma$>^[[Ma$> > >> >> >> ?? ?? ?? click: ^[[M 9=^[[M#9= > >> >> >> > >> >> >> Inside tmux (one pane): > >> >> >> ?? ?? ?? scroll-up: ^[[M`"C^[[M`"C > >> >> >> ?? ?? ?? scroll-down: ^[[Ma"@^[[Ma"@ > >> >> >> ?? ?? ?? click: ^[[M "?^[[M#"? > >> >> >> > >> >> >> Inside tmux (>1 pane): > >> >> >> ?? ?? ?? scroll-up: ^[[M`"(^[[M`"( > >> >> >> ?? ?? ?? scroll-down: ^[[Ma")^[[Ma") > >> >> >> ?? ?? ?? click: ^[[M 2.^[[M#2. > >> >> >> > >> >> >> A part of the codes change every time I repeat the `cat' part, cat > >> >> >> click = a code, ctrl-C, cat click = a new code. > >> >> >> So I hope this is info you wanted. > >> >> >> > >> >> >> > >> >> >> ----- > >> >> >> Florian. > >> >> >> / For security reasons, all text in this mail > >> >> >> ?? is double-rot13 encrypted. / > >> >> >> > >> >> >> > >> >> >> ------------------------------------------------------------------------------ > >> >> >> This SF.net Dev2Dev email is sponsored by: > >> >> >> > >> >> >> Show off your parallel programming skills. > >> >> >> Enter the Intel(R) Threading Challenge 2010. > >> >> >> http://p.sf.net/sfu/intel-thread-sfd > >> >> >> _______________________________________________ > >> >> >> tmux-users mailing list > >> >> >> tmux-users@lists.sourceforge.net > >> >> >> https://lists.sourceforge.net/lists/listinfo/tmux-users > >> >> > > >> >> > ------------------------------------------------------------------------------ > >> >> > This SF.net Dev2Dev email is sponsored by: > >> >> > > >> >> > Show off your parallel programming skills. > >> >> > Enter the Intel(R) Threading Challenge 2010. > >> >> > http://p.sf.net/sfu/intel-thread-sfd > >> >> > _______________________________________________ > >> >> > tmux-users mailing list > >> >> > tmux-users@lists.sourceforge.net > >> >> > https://lists.sourceforge.net/lists/listinfo/tmux-users > >> >> > > >> >> > > >> > > >> > > > > > ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
