On Fri, Feb 21, 2014 at 10:31 AM, Thomas Adam <tho...@xteddy.org> wrote:
> On 21 February 2014 09:27, Carsten Mattner <carstenmatt...@gmail.com> wrote:
>> On Fri, Feb 21, 2014 at 9:40 AM, Thomas Adam <tho...@xteddy.org> wrote:
>>> On 21 February 2014 08:35, Carsten Mattner <carstenmatt...@gmail.com> wrote:
>>>> What's the status of implementing flow control to prevent tmux from
>>>> getting unresponsive of a wall of text is quickly printed?
>>>
>>> See:
>>>
>>> c0-change-{,trigger,interval}
>>
>> The default values of c0-change-{trigger,interval} 250 and 100 seem
>> reasonable
>> but don't prevent lockups. So there must be something else that needs fixing.
>
> Well, not always. It depends how much text is being sent, even if
> that *is* the actual problem, though. What else triggers this if it's
> not just large amounts of text?
For me it's always quick printing of a lot of text. gunzip a tarball to stdout
and you'll reproduce the temporary lockup.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
