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))
+ return;
+
yoff = wp->yoff;
if (status_at_line(c) == 0)
yoff++;
On Thu, Mar 07, 2013 at 08:40:53PM +0000, Nicholas Marriott wrote:
> 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 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/urandom | head -n 10; sleep 1; done
> > 3 - focus the bottom pane and zoom it
> >
> > Not sure if relevant by my OS is archlinux, shell is zsh and terminal is
> > urxvt.
> >
> > On Thu, Mar 7, 2013 at 7:12 AM, Nicholas Marriott
> > <nicholas.marri...@gmail.com> wrote:
> > > 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 about my workflow
> > >>
> > >> 1- split window with top pane running shell or node.js server web server
> > >> 2- bottom pane running vim, which is most of the time zoomed
> > >> 3- when I edit and save a file in vim, a background watcher process
> > >> restarts the web server, often causing it to output some information.
> > >>
> > >> Sometimes when I execute step 3 I can see the webserver output on the
> > >> vim window, exactly where the pane would be if it were not hidden,
> > >> except that it overrides vim output and there is no pane separator.
> > >>
> > >> Since this doesn't happen always I could not figure the steps to
> > >> reproduce it, but I guess that if you run a process that continuously
> > >> outputs data(eg: tail or a shell loop) in a pane hidden by zoom
> > >> there's a good chance this will happen
> > >>
> > >> ------------------------------------------------------------------------------
> > >> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> > >> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> > >> endpoint security space. For insight on selecting the right partner to
> > >> tackle endpoint security challenges, access the full report.
> > >> http://p.sf.net/sfu/symantec-dev2dev
> > >> _______________________________________________
> > >> tmux-users mailing list
> > >> tmux-users@lists.sourceforge.net
> > >> https://lists.sourceforge.net/lists/listinfo/tmux-users
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
