You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I am using hatcog in my tmux, I notice that tmux is often noting activity in idle chat windows. I believe this is because the "last ping" number is updating in the corner. I don't want to set monitor-activity off, because I really want to see when people are chatting in the channels.
I think what would be best is a configuration option to disable updates the last ping display (possibly user count changes as well) except when the user is actively typing or sending a message. It would be "use at your own risk" because it defeats the purpose of the last ping field, but it is more congruent with tmux activity notifications.
The text was updated successfully, but these errors were encountered:
The default 'monitor-activity' behavior in tmux will show activity when
something changes on the screen. This will get triggered by multiple
things, like the ping time update, a change in the number of total or
active users, or signon-signoff-nickchange messages. This change adds a
'chatonly' configuration option that supresses all of the above, thus
ensuring that tmux will only see activity that is actual chat traffic.
Closes: grahamking#19
When I am using hatcog in my tmux, I notice that tmux is often noting activity in idle chat windows. I believe this is because the "last ping" number is updating in the corner. I don't want to set monitor-activity off, because I really want to see when people are chatting in the channels.
I think what would be best is a configuration option to disable updates the last ping display (possibly user count changes as well) except when the user is actively typing or sending a message. It would be "use at your own risk" because it defeats the purpose of the last ping field, but it is more congruent with tmux activity notifications.
The text was updated successfully, but these errors were encountered: