On 06/03/14 12:44, Thomas Adam wrote:
> On 5 March 2014 23:40, Jan Larres <j...@majutsushi.net> wrote:
>> No, it happens without me doing anything. Now that I think about it the
>> rate may be related to my statusline update interval (1 second), but
>> unfortunately I can't test that any more as I had to restart tmux to be
>> able to continue working.
>
> So take out the call to tmux-status as you have it declared at the
> moment; does that make this go away?

Like I said I had to restart tmux so I can't test that at the moment,
but I could try to reproduce it. I noticed though that in the current
development version the 'info' command doesn't seem to report the
session information any more, only the terminal information. That
command also isn't documented in the man page so I don't know if I need
any additional switches for that.

-Jan


------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users

Reply via email to