Re: bug with mode-mouse on

2013-03-07 Thread Georgios Choudalakis
Hi Nicholas, sorry for the delay, I had to go yesterday. Today I tried the line you sent me: tmux -uLtest -v new\; set -g utf8-mouse on\; set -g mouse-select-pane on\; splitw tmux didn't manage to start; it complained about the command "utf8-mouse". Did you mean "mouse-utf8" instead? I guess

Re: Hidden pane sometimes 'leaking' output into zoomed window

2013-03-07 Thread Nicholas Marriott
Are you sure you restarted completely with this fix? I can't reproduce now and it has been running for 15 minutes or so. Don't worry about what happens when you unzoom or got to the other pane, you can't write random crap to the terminal without eventually causing some problem or other. I only car

Re: Hidden pane sometimes 'leaking' output into zoomed window

2013-03-07 Thread Nicholas Marriott
Actually, try this please: diff --git a/screen-redraw.c b/screen-redraw.c index 899f741..14b7316 100644 --- a/screen-redraw.c +++ b/screen-redraw.c @@ -273,6 +273,9 @@ screen_redraw_pane(struct client *c, struct window_pane *wp) { u_int i, yoff; + if (!window_pane_visible(wp)) +

Re: Hidden pane sometimes 'leaking' output into zoomed window

2013-03-07 Thread Nicholas Marriott
You see this eventually even if you zoom the bottom pane and don't unzoom it? Does it still happen if you set allow-rename to off? On Thu, Mar 07, 2013 at 08:42:00AM -0300, Thiago Padilha wrote: > Ok I managed to reproduce. It seems that when certain bytes are output > on the hidden pane the bu

Re: Hidden pane sometimes 'leaking' output into zoomed window

2013-03-07 Thread Thiago Padilha
Ok I managed to reproduce. It seems that when certain bytes are output on the hidden pane the bug is triggered(the webserver outputs some colored chararacted sometimes). Try this: 1 - split the pane in two 2 - on the top pane enter this(or equivalent for your shell/os): while true; do cat /dev/ura

Re: Hidden pane sometimes 'leaking' output into zoomed window

2013-03-07 Thread Nicholas Marriott
I don't see this even with very fast output and I don't see any obvious way it can happen. Can you try to come up with an easier way to reproduce? On Wed, Mar 06, 2013 at 11:37:55AM -0300, Thiago Padilha wrote: > I could not find the exact conditions that cause this, but here > certain facts abou

Re: send-keys not working with a target that has a . in the session name.

2013-03-07 Thread Nicholas Marriott
Try a trailing period: "wraithan.net:3." On Wed, Mar 06, 2013 at 11:13:59PM -0800, Wraithan (Chris McDonald) wrote: > (pytmux)wraithbook:pytmux cmcdonald$ tmux send-keys -t wraithan.net:3 > "workon wraithan.net && git pull" ^M > session not found: wraithan > (pytmux)wraithbook:pytmux cmcdonald$